You are on page 1of 72

IntegrateIT

Aspect Integrator PlatformTM


Version 2.0

National Language Support


Translator’s Guide
IntegrateIT
Aspect Integrator PlatformTM
Version 2.0

National Language Support


Translator’s Guide
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Automation Technology Products. ABB Automation
Technology Products. assumes no responsibility for any errors that may appear in this
document.

In no event shall ABB Automation Technology Products be liable for direct, indirect, spe-
cial, incidental or consequential damages of any nature or kind arising from the use of
this document, nor shall ABB Automation Technology Products be liable for incidental or
consequential damages arising from use of any software or hardware described in this
document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Automation Technology Products, and the contents thereof must not
be imparted to a third party nor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.

© Copyright 2001-2002 ABB. All rights reserved.

Release: June 2002


Document number: 3BSE 025 113R301

TRADEMARKS
Registrations and trademarks used in this document include:

The IndustrialIT wordmark and all product names in the form XXXXXXIT mentioned herein
are registered or pending trademarks of ABB.

Microsoft Registered trademark of Microsoft Corporation.

Windows Registered trademark of Microsoft Corporation.

Windows 2000 and MS-DOS Registered trademarks of Microsoft Corporation.

ActiveX and Visual Basic Registered trademarks of Microsoft Corporation.

PostScript Registered trademark of Adobe Systems Inc.

Acrobat Reader Registered trademark of Adobe Systems Inc.

Ghost Registered trademark of Symantec Corporation.

Aspect Integrator Platform Trademark of ABB Ltd., Switzerland.

Aspect Studio Trademark of ABB Ltd., Switzerland.

Aspext Express Trademark of ABB Ltd., Switzerland.

Process Portal Trademark of ABB Ltd., Switzerland.


TABLE OF CONTENTS

About This Book


0.1 General ........................................................................................................................9
0.2 Use of Warning, Caution, Information, and Tip Icons ................................................9
0.3 Document Conventions .............................................................................................10
0.4 Terminology...............................................................................................................11
0.5 Related Documentation .............................................................................................17

Section 1 - Introduction
1.1 The National Language Support (NLS) in
Aspect Integrator PlatformTM ..............................................................................19
1.1.1 Unicode .......................................................................................................20
1.1.2 Direction of Text .........................................................................................20
1.2 The Translation Task .................................................................................................21

Section 2 - Getting Started


2.1 About this Chapter.....................................................................................................23
2.2 Where to Work?.........................................................................................................23
2.3 Required Programs and other Equipment..................................................................23
2.4 An NLS Compact Disk for Translators .....................................................................24
2.5 Required Log on Privileges .......................................................................................24
2.6 Starting Plant Explorer Workplace ............................................................................25

Section 3 - On-line Manuals


3.1 About this Section .....................................................................................................27
3.2 Translating User’s Guides .........................................................................................27
3.3 Word Processing during Translation..........................................................................28

3BSE 025 113R301 5


Table of Contents

3.4 Preparing Translated Files .........................................................................................28


3.5 Making PDF Files of On-line Manuals .....................................................................29
3.6 Renaming PDF Files..................................................................................................30
3.7 Pasting PDF Files in
Process Portal File Structure for a Test ................................................................30

Section 4 - On-line Help


4.1 About this Section .....................................................................................................33
4.2 Preparations ...............................................................................................................34
4.3 Topics.........................................................................................................................34
4.4 Help Buttons ..............................................................................................................36
4.4.1 On-line Help Marker in English Original File ............................................36
4.5 Pasting Marker Text in Translated File .....................................................................39
4.5.1 Processing Help Files ..................................................................................39
4.5.2 Renaming On-line Help Files......................................................................39
4.6 Pasting CHM Files in Process Portal File Structure..................................................40

Section 5 - Translating
Static Resources (DLL Files)
5.1 About this Section .....................................................................................................43
5.2 Background................................................................................................................43
5.3 Preparations ...............................................................................................................43
5.4 Copying DLLs from a System Product .....................................................................44
5.5 Using the Localization Tool ......................................................................................45
5.5.1 Strings that must not be Translated .............................................................45
5.6 Pasting Translated DLLs to
the Client File Structure for Test ..........................................................................46

Section 6 - Translating Workplace Windows, Faceplates etc.


6.1 About this Section .....................................................................................................49
6.2 Extracting Aspect Data..............................................................................................49
6.3 Translate DLLs in the Localization Tool...................................................................51
6.4 Loading Translation into the Process Portal for Test.................................................52

3BSE 025 113R301 6


Table of Contents

Section 7 - Creating an Extension Pack


with Translated Files
7.1 About this Section .....................................................................................................55
7.2 Installing Product Packager .......................................................................................55
7.3 Preparations before Creating an Extension Pack.......................................................56
7.4 How to create an Extension Pack ..............................................................................56

Appendix A - Language Abbreviations etc.


A.1 Language and Associated Abbreviations .................................................................63
A.2 Restrictions in Translation of some DLL Strings .....................................................65

Appendix B - On-line Help Procedure


B.1 To work with WebWorkPublisher and HTML Workshop ........................................67

INDEX ..........................................................................................................................69

3BSE 025 113R301 7


Table of Contents

8 3BSE 025 113R301


About This Book

0.1 General
The main purpose of the National Language Support Translator’s Guide is to
describe how to create a new user interface language in ABB IndustrialIT products.
The user interface is defined as all the information the operator can reach from the
screen when logged on with operator privileges. Consequently not only texts in
windows, dialog boxes etc. have to be translated but also On-line Help texts and
On-line Manuals.
The language that you are translating to is called the target language (or your local
language).

0.2 Use of Warning, Caution, Information, and Tip Icons


This publication includes Warning, Caution, and Information texts where
appropriate, to point out safety related or other important information. It also
includes Tip to point out useful hints to the reader. The corresponding symbols
should be interpreted as follows:

Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.

3BSE 025 113R301 9


Document Conventions

Caution icon indicates important information or warnings related to the concept


discussed in the text. It might indicate the presence of a hazard which could result in
corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to use
a certain function.

Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.

0.3 Document Conventions


The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).

10 3BSE 025 113R301


Terminology

The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
• System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name

0.4 Terminology
The list contains terms and abbreviations that are unique to ABB or have a usage or
definition that is different from standard industry usage.

Term Description
ActiveX Microsoft standard for user interface components, based
on definition of software interfaces.
Aspect An aspect is a description of some properties of a real
world entity. The properties described could be
mechanical layout, how the object is controlled, a live
video image, name of the object etc. In the Aspect
Integrator Platform is an aspect residing in an Aspect
Object. Some examples of aspects are circuit diagram,
process display and control logic.

3BSE 025 113R301 11


Terminology

Term Description
Aspect Category A specialization of an aspect type. For example, the
aspect type Graphic Display includes the categories
Overview, Group and Object Display.
Aspect Integrator A collection of software that forms the basis for an
Platform IndustrialIT System, and provides the development and
execution environment for IndustrialIT compliant
applications. The Aspect Integrator Platform includes the
Aspect Framework.
Aspect Objects A computer representation of a real world entity like a
pump, a valve, an order or a virtual object like a service.
This computer representation is implemented by the
Aspect Integrator Platform. An Aspect Object works like
an information container for it’s aspects.
Aspect Object Type An Aspect Object Type defines certain characteristics
that are shared between several Aspect Object
instances, such as a basic set of common aspects.
This makes it possible to create and efficiently re-use
standardized solutions to frequently recurring problems.
For example, rather than building an Aspect Object from
scratch for every valve in a plant, you can define a set of
valve types, and then create all valve objects of these
instances.
Aspect Server A server that runs the central functions of the Aspect
Object architecture, such as Aspect Directory, Structure
and Name Server, Cross Referencing, File Set
Distribution, etc.
Aspect System A software system, which implements one or several
aspect types by providing one or several aspect system
objects.
Client Client is the part of the software that supply data to a
subscriber.
Client/Server Network A client/server network is used for communication
between servers, and between workplaces and servers.

12 3BSE 025 113R301


Terminology

Term Description
Connectivity Product Connectivity components, up-loader, supporting aspect
systems (e.g for the configuration), and graphical
elements, faceplates, Aspect Object Types, etc.,
bundled together to provide the integration of a certain
type of devices into the IndustrialIT system.
Connectivity Server A server that provides access to controllers and other
sources for real-time data, historical data, and alarm and
event data. A Connectivity Server runs services related
to OPC/DA, OPC/AE, OPC/HDA and SysMag.
Faceplate A faceplate is an aspect that provides a graphical
representation of a certain aspect object, with
presentation of certain properties related to the object,
and mechanism for operator interaction such as on/off,
increase/decrease, etc. Aspect Object types often
include several faceplate aspects, providing different
presentation and interaction possibilities.
Graphic Display A graphic display is an aspect that provides a visual
presentation. It consists of static graphics representing
for example tanks, pipes etc., and graphic elements that
present dynamic information. Graphic displays are often
used to present the state of a process or a part of a
process, but are useful in any context where dynamic
graphical information is needed.
IndustrialIT ABB’s vision for enterprise automation.
IndustrialIT System A computer system that implements (part of) the
IndustrialIT vision. Aspect Integrator Platform is an
example of such a system.
Node A computer communicating on a network e.g. the
Internet, Plant, Control or IO network. Each node
typically has a unique node address with a format
depending on the network it is connected to.

3BSE 025 113R301 13


Terminology

Term Description
OPC An application programming interface defined by the
standardization group OPC Foundation. The standard
defines how to access large amounts of real-time data
between applications. The OPC standard interface is
used between automation/control applications, field
systems/devices and business/office application.
Plant Explorer An application that is used to create, delete and
organize Aspect Objects and Aspects within the Aspect
Integrator Platform. The plant explorer organizes the
Aspect Objects in structures according to functionality,
location etc.You can also use it to browse and search the
structures of the plant.
Process Portal A IndustrialIT System Product containing functionality for
efficient control and supervision of an automated
process. Key functions are presentation of graphics,
process dialogs and presentation of alarms and trends.
Permission A permission groups a set of operations that require the
same authority. For each operation defined for an
aspect, the aspect category specifies the permission
needed to use that interface.
Process Object A process concept/equipment e.g. valve, motor,
conveyor or tank.
Product Family A range of products within a Product Suite, forming a
scalable offering.
Examples: a range of controllers, a family of I/O
Products.
Product Suite Product with similar functionality are kept together in a
suite. Suite names have a superscripted IT-suffix.
Examples: OperateIT, ControlIT, IntegrateITetc.
Property A data field on an aspect of an Aspect Object that can be
accessed through OPC using the standard Aspect
Object reference syntax.
A data field on an ActiveX control accessible from the
Visual Basic editor.

14 3BSE 025 113R301


Terminology

Term Description
Security Security controls a user’s authority to perform different
operations on Aspect Objects, depending on several
parameters:
• The user’s credentials, as provided by Windows
• The node where the user is logged in. This makes it
possible to give a user different authority depending
on where he/she is located, e.g. close to the
process equipment, in a control room, or at home
accessing the system through Internet.
• The operation the user wants to perform the
operation on.
Server A node that runs one or several Afw Services.
It is the part of the software that supply data to a
subscriber.
Structure A hierarchical tree organization of Aspect Objects.
Each structure is used to define a certain kind of relation
between Aspect Object. The functional structure defines
how a function can be divided into sub functions, the
location structure defines how different objects are
located within each other.
The control structure defines how functions are
executed by tasks, controllers etc. An Aspect Object can
be located in several structures, for example both in a
functional structure and in a location structure.
System Application A software package that provides functionality in the
IndustrialIT System. System applications cooperate
according to rules defined by the IndustrialIT
architecture, using mechanism provided by the Aspect
Integrator Platform. They are normally bundled into
System Products. To participate in Aspect Object
operations, and thus be an integrated part of an
IndustrialIT system, a system application must present
itself as an aspect system. When there is no risk for
confusion with user application, the term application may
be used instead of system application.

3BSE 025 113R301 15


Terminology

Term Description
System Extension A system Extension consists of one or more applications
that are bundled as an extension to one or several
existing System Product(s). A System extension can
only be installed if (one of) the corresponding System
Product(s) has been installed previously.
System Product A system product consists of applications bundled
together with relevant parts of the Aspect Integrator
Platform. It is complete from installation point-of-view,
and requires only Windows 2000. Several System
Products can be installed on the same physical node.
Uploader An upload is used to import a configuration from
devices, to read in and build a set of Aspect Objects
from information present in the devices.
User application A configuration of software and hardware components
that applies to a specific problem, e.g. a specific process
control problem. A user application consists of a set of
simple and composite Aspect Object instances, with
parameter values and other configuration data for the
aspects, e.g control logic, graphics, alarm and event
specifications, reports etc.
View An Aspect can have several ways to be presented
depending on the task performed, like viewing or
configuration. Each presentation form is called a view.
Workplace 1. User interactive functions that are combined for a
particular use, e.g, Operator Workplace.
2. A node that runs one or several workplace
applications.

16 3BSE 025 113R301


Related Documentation

0.5 Related Documentation

Category Title Description


Installation IntegrateIT Aspect Integrator Platform This book describes how you install the
and System SDK Aspect Integrator Platform SDK,
Administration Installation Guide including the requirements on the
hardware.
IntegrateIT Aspect Integrator Platform This book describes how you install the
Run-time Aspect Integrator Platform Run-time,
Installation Guide including the requirements on the
hardware.
IntegrateIT Aspect Integrator Platform This book describes how you configure
Administrator’s Guide products built on the Aspect Integrator
Platform and how you then perform
maintenance.
IntegrateIT Aspect Integrator Platform This book describes how to set security
Security in products built on the Aspect Integrator
Reference Manual Platform.
Software IntegrateIT Aspect Integrator Platform This book describes a view of the
Development Integration Guideline available application tools, techniques
and development environments for
system developers.
IntegrateIT Aspect Integrator Platform This book describes the IntegrateIT
Architecture Document architecture in details.
IntegrateIT Aspect Integrator Platform This book provides a number of
Automation Models examples on how to use the Automation
Programmer’s Guide Models.
IntegrateIT Aspect Integrator Platform This book contains a comprehensive
Programmer’s Guide description of how to program the
Aspect Integrator Platform.

3BSE 025 113R301 17


Related Documentation

Category Title Description


Software IntegrateIT Aspect Studio This book describes Aspect Studio
Development User’s Guide excluding Aspect Express (which is
(cont.) described in a separate User’s Guide).
IntegrateIT Aspect Express This book describes everything about
User’s Guide Aspect Express including installation.
Software IntegrateIT Aspect Integrator Platform This book describes how to engineer the
Engineering Basics IntegrateIT.
Reference Manual
IntegrateIT Aspect Integrator Platform This book describes how o use
Predefined Aspects predefined aspects, such as property
Reference Manual transfer and translation.
IntegrateIT Aspect Integrator Platform This book describes everything about
Workplace and Plant Explorer the user interface, for example how you
Reference Manual present information, navigate and
control objects.
IntegrateIT Aspect Integrator Platform This book explains how to use the
Alarm and Event Aspect Integrator Platform Alarm and
Reference Manual Event functions. It covers alarm and
event configuration and presentation.
IntegrateIT Aspect Integrator Platform This book describes how to configure
Graphics and use graphic aspects in Aspect
Reference Manual Integrator Platform.
IntegrateIT Aspect Integrator Platform This book covers how to use the
Graphics Builder Graphics Builder software to create
Reference Manual graphic aspects.
IntegrateIT Aspect Integrator Platform This book describes the building blocks
Graphics Standard Building Blocks provided by ABB for the graphics in
Reference Manual Aspect Integrator Platform.
IntegrateIT Aspect Integrator Platform This book describes how to use the
Trends and Historian Historian data logging and Trend graphs
Reference Manual to view historical data.

18 3BSE 025 113R301


Section 1 Introduction The National Language Support (NLS) in Aspect Integrator PlatformTM

Section 1 Introduction

1.1 The National Language Support (NLS) in


Aspect Integrator PlatformTM
In order to make the translation (localization) of the user interfaces and other
products within the IndustrialIT concept easier, the National Language Support
concept is integrated in Aspect Integrator Platform (AIP). NLS comprises a set of
aiding program modules built to harmonize with the Windows language settings and
in this way the IndustrialIT products have been given a multilingual capacity.
In Windows the local language can be set directly in the Regional Settings.
If a sufficient translation has been made, the new language will be displayed on the
screen. The NLS implemented in this product is, however, not a direct help program
for the translation itself, but necessary for a smooth translation.

3BSE 025 113R301 19


Unicode Section 1 Introduction

Plant network

Client (computer for the


Aspect Server operator where
Process PortalTM can run)

Control network Connectivity Server


Masterbus

Controller

Local I/O Remote I/O (located near the object)

Figure 1-1 A typical configuration of a Control System

1.1.1 Unicode
IndustrialIT products support Unicode (used in Windows). Unicode is created to
support character sets for foreign languages, at present over a hundred languages.
More information on Unicode can be found on Microsoft’s home page.

1.1.2 Direction of Text


The only direction of text that is accepted is from left to right. A top to bottom or
right to left direction of text is not supported by the system.

20 3BSE 025 113R301


Section 1 Introduction The Translation Task

1.2 The Translation Task


The translation of the user interface features the following steps:
1. On-line Manuals are an electronic variant of the printed User’s Guides -
files prepared in PDF file format. See Section 3, On-line Manuals.
(To be accurate, the On-line Manual concept contains more manuals, but they
will not be translated - since they are intended for other user groups.)
2. On-line Help sections are created as conditional texts in the word processing
program, FrameMaker, used when developing User’s Guides. See Section 4,
On-line Help.
3. Workplace Texts, Dialog Boxes, Buttons, Labels etc. are all examples of
static texts, exported from Process PortalTM as resource DLL files for
translation in separate software. See Section 5, Translating Static Resources
(DLL Files).
4. Workplace Windows, Faceplates etc. are examples of aspect data.
They contain text that will be displayed in Workplaces and therefore have
to be translated. They can be exported as resource DLLs and then translated
as mentioned in step 3 above. See Section 6, Translating Workplace Windows,
Faceplates etc.
External Messages such as Alarm, Status, History Trends. Messages from
controllers will not be handled in this translation. The majority of these messages
are already translated since these applications very often are created locally.

The translation of screen information, according to Step 3 and Step 4 above,


includes text and numbers referred to as text. The localization process does
not include any other type of adaptation, for example color, typeface, style.

3BSE 025 113R301 21


The Translation Task Section 1 Introduction

22 3BSE 025 113R301


Section 2 Getting Started About this Chapter

Section 2 Getting Started

2.1 About this Chapter


This section contains information about what you need to get started and how to
start the Workplace.

2.2 Where to Work?


All translation work can be carried out on one of the clients connected to the system,
or on a separate computer. It is however essential that you have access to a client for
export and import procedures.

2.3 Required Programs and other Equipment


The following programs and equipment are necessary for carrying out the
translation of the user interface:
• The product installed on a system together with Aspect StudioTM
• Adobe Framemaker version 6.0 or later
• Adobe Acrobat version 4.0 or later
• WebWorks Publisher Pro version 6.0 or later (http//www.webworks.com)
• HTML Help Workshop version 4.74 or later
• Localization Tool, for example RCWinTrans, Visual Localize, or similar
• HyperSnap-DX Pro (http//www.hyperionics.com)
• Helvetica and Times New Roman Fonts in the computer where FrameMaker
files are handled (recommended)
• A black & white PostScript printer or an Acrobat PDF Writer

3BSE 025 113R301 23


An NLS Compact Disk for Translators Section 2 Getting Started

2.4 An NLS Compact Disk for Translators


The NLS Translator’s Guide is distributed together with a CD containing the
following print files. Please note that this is an example of the contents on your CD.
The example is taken from Process Portal A:
• FrameMaker files for the relevant books:
– Operator’s Guide
– Workplace and Plant Explorer, User’s Guide
– Alarm and Event Manager, User’s Guide
– Trends and Historian, User’s Guide
• Template named ABB HTML HELP for On-line Help used in WebWorks
Publisher
• The following Help files:
– operate_help.h
– work_help.h
– alarm_help.h
– trend_help.h

2.5 Required Log on Privileges


Administrator privileges are necessary.

24 3BSE 025 113R301


Section 2 Getting Started Starting Plant Explorer Workplace

2.6 Starting Plant Explorer Workplace


We assume that the system is running and you are logged on to the client (computer)
on which you will carry out your translation work and that the server is running.
If not, see IntegrateIT Workplace and Plant Explorer Reference Manual.
1. On the desktop, right click My ePlant icon. See Figure 2-1.

Figure 2-1 The ePlant icon

2. Select Plant Explorer from the menu. The Plant Explorer Workplace will now
be displayed on your screen. See Figure 2-2.

Figure 2-2 The Plant Explorer Workplace

3BSE 025 113R301 25


Starting Plant Explorer Workplace Section 2 Getting Started

You have now started your system and can go on to the following sections:
• Section 3, On-line Manuals
• Section 4, On-line Help
• Section 5, Translating Static Resources (DLL Files)
• Section 6, Translating Workplace Windows, Faceplates etc.
• Section 7, Creating an Extension Pack with Translated Files

26 3BSE 025 113R301


Section 3 On-line Manuals About this Section

Section 3 On-line Manuals

3.1 About this Section


This section deals with how to create On-line Manuals from the translated
User’s Guides. The task described here can be carried out on a separate computer,
except for importing the translated files to the file structure and carrying out
some tests.

3.2 Translating User’s Guides


For Process Portal A the following guides are intended for operators and
have to be translated:
• Operator’s Guide
This book describes a number of selected operator scenarios.
• Workplace and Plant Explorer, User’s Guide
This book describes the user interface, for example how you present
information, navigate and control objects.
• Alarm and Event Manager, User’s Guide
This book explains how to use the Alarm and Event functions in
Aspect Integrator Platform. It covers alarm and event configuration and
presentation.
• Trends and Historian, User’s Guide
This book describes how to use the trend graphs and historian to view historical
data during runtime.

3BSE 025 113R301 27


Word Processing during Translation Section 3 On-line Manuals

3.3 Word Processing during Translation


The translation has to be carried out in FrameMaker 6.0 or a later version.
Please note that there is a number of cross-references and corresponding
anchors in the text. The cross-references are marked in blue text and the
anchors are represented by this sign ( ). The anchors are hard to keep
during translation and we therefore recommend that you erase all anchors.
If you have difficulties in restoring anchors in your target text, please look
in the original files for the original cross-reference.
When you erase the anchors you will also erase a number of On-line Help
Markers ( ). How to restore markers is explained in Section 4, On-line
Help.

The translation is assumed to be carried out by professional translators.


Very little is therefore mentioned here about the translation process.
“The GUI Guide” from Microsoft has to be followed.
A good idea is to start the translation work with the variables prepared for
the Process Portal manuals. The Figure and Table formats need to be
translated as well as the Cross-reference formats (Appendix etc.).

3.4 Preparing Translated Files


The books adapted for translation have to be prepared in the following way:
1. Open one of the translated books and then one of the files in the book.
2. Select Conditional Text from the Special menu and click Show/Hide.
3. Select Print Only and click Apply and Save.
4. In the book, select Import and Formats... from the File menu and deselect all
Import Formats excepting Conditional Text Settings.
5. Check that all files are selected for update except TOC and IX files.
Click Import.
6. Repeat the steps above for all translated User’s Guides.

28 3BSE 025 113R301


Section 3 On-line Manuals Making PDF Files of On-line Manuals

3.5 Making PDF Files of On-line Manuals


The User’s Guides shall now be saved as PDF files.
1. On the computer where FrameMaker is used for translation, select a black &
white printer for PostScript.
2. Open the book file for one of the User’s Guides and create a PDF file by
selecting Save As.
3. In the Save As dialog box, select PDF.
4. Replace the fm file extension with pdf.
5. Click Save. The Acrobat Setup window will now be displayed.
6. Make the following settings in the window. See Figure 3-1.

Figure 3-1 Settings in the Acrobat Setup window

7. Repeat the steps above for all User’s Guides.

3BSE 025 113R301 29


Renaming PDF Files Section 3 On-line Manuals

3.6 Renaming PDF Files


1. Add the language code to the PDF file names. If the file name for example is
3BSE017084_Workplace_Book.pdf
change the Swedish file name to
3BSE017084_Workplace_Book_SVE.pdf.
SVE is the language abbreviation of Swedish. For more information on
language abbreviation. See Appendix A, Language Abbreviations etc.

3.7 Pasting PDF Files in


Process Portal File Structure for a Test
The PDF-files can now be pasted into the structure for testing before creating an
Extension Pack. See Section 6, Translating Workplace Windows, Faceplates etc.
1. Create a new sub-folder under On-line Manuals with the language
abbreviation (SVE for Swedish etc.). See Figure 3-2. For language
abbreviation. See Appendix A, Language Abbreviations etc..

Figure 3-2 Folder Structure of On-line Manual folder

30 3BSE 025 113R301


Section 3 On-line Manuals Pasting PDF Files in Process Portal File Structure for a Test

2. Paste all the renamed PDF files in the new folder.


3. The new folder will not contain all On-line Manuals. A number of manuals are
still in US English (not intended to be shown in the operator user interface - but
for other user categories).
The Regional Settings can now be selected and after that a test can be performed.
4. Stop the system by using the Configuration Wizard.
5. In the Control Panel click Regional Option and select the name of the target
language in the language code drop down combo box.
6. Start the system again.
7. Check the system settings for the target language and click OK.
8. Click Apply and then OK.
9. Press Ctrl+Alt+Del and log off.
10. Change the privileges from Administrator to Operator.
11. Log on again and start Process Portal.
12. Check that all On-line Manuals, that can be reached from the operator
privileges, are in your local language. If you log on with Administrator
privileges you can reach manuals that have not been translated.
13. When the On-line Manuals are checked, an Extension Pack shall be generated
and used for upgrading an Installed System Product with the target language.
See Section 7, Creating an Extension Pack with Translated Files.

3BSE 025 113R301 31


Pasting PDF Files in Process Portal File Structure for a Test Section 3 On-line Manuals

32 3BSE 025 113R301


Section 4 On-line Help About this Section

Section 4 On-line Help

4.1 About this Section


This section describes how to create a new language version of the On-line Help
created in FrameMaker as conditional text. There are other methods used in other
documents within the IndustrialITconcept, but handling of these files will not be
mentioned here.
Please note that only the On-line Help that is meant for translation is mentioned
here. The On-line Help for Process Portal is created from the following
User’s Guides:
• Operator’s Guide
• Workplace and Plant Explorer, User’s Guide
• Alarm and Event Manager, User’s Guide
• Trends and Historian, User’s Guide
Conventional On-line Help normally contains the following:
• Topics
• Help Buttons
• Context sensitivity function (not implemented in this version)
• Tool Tips are implemented as DLL files see Section 5, Translating Static
Resources (DLL Files).

The task described here can be performed on a separate computer, excepting


pasting the translated and compiled On-line Help files in the file structure
and carrying out some tests.

3BSE 025 113R301 33


Preparations Section 4 On-line Help

4.2 Preparations
Check that the following programs are installed on the computer on which you are
going to prepare the On-line Help file:
• Adobe FrameMaker version 6.0 or later
• WebWorks Publisher Pro version 6.0 or later
• HTML Help Workshop version 4.74 or later
For Aspect Integrator Platform, also check that the following files are installed on
your computer:
• ABB HTML HELP (template files)
• operate_help.h
• work_help.h
• alarm_help.h
• trend_help.h
Check that the following FrameMaker books with all corresponding files are copied
to your computer (read/write)
• Operator’s Guide
• Workplace and Plant Explorer, User’s Guide
• Alarm and Event Manager, User’s Guide
• Trends and Historian, User’s Guide
Finally, check that all files have read/write status.

4.3 Topics
The On-line Help is created primarily from the text body of the User’s Guides.
Only small changes are made as conditional text. Therefore the translation of the
User’s Guides can be carried out as part of the translation of On-line Manuals (see
Section 3, On-line Manuals). In a second step the On-line Help modification can be
made as described below. When this translation has been carried out and the Help

34 3BSE 025 113R301


Section 4 On-line Help Topics

Button markers have been added, the help files can be processed in WebWorks
Publisher and HTML Workshop.
1. Open one of the translated books and then one of the files in the book.
2. Select Conditional Text from the Special menu and click Show/Hide.
3. Select On-line Help Only and click Apply and Save.
4. In the book, select Import and Formats... from the File menu and deselect all
Import Formats except for Conditional Text Settings.
5. Check that all files are selected for update except for TOC and IX files.
Click Import.
6. Use the Find/Change tool to find conditional text (On-line Help Only) and
translate this text where it is found.
7. Carry out the same procedure for all files in all books.

3BSE 025 113R301 35


Help Buttons Section 4 On-line Help

4.4 Help Buttons


The Help button identity corresponds to a marker in the FrameMaker text, which
shall be displayed when the Help button is pressed. The marker has a name that
corresponds to the identity. See Figure 4-1.

Marker identity in FrameMaker


VHN_WORKPLACE_LAYOUT

Identity in IndustrialIT
[;;

Figure 4-1 Help Button Identity in IndustrialIT User Interface and FrameMaker

4.4.1 On-line Help Marker in English Original File


During the translation process it is recommended to erase the help text markers.
Therefore, the following method is the safest way to restore markers after
translation.

36 3BSE 025 113R301


Section 4 On-line Help On-line Help Marker in English Original File

1. Perform Step 1 through Step 5 under Topics on page 34.


2. Open the first English file (Section 1) and select Generate/Book from the
File menu.
3. Select List of Markers in the Generate/Book window and click on
Generate...
4. Check in the Set up List of Markers window that the
ProgramLinkToHelpTopic format is selected.
5. Un-check the Create Hypertext Links check box.
6. Click Generate...
FrameMaker will now generate a list of markers. If there are no markers in the file,
the list will be empty. If empty, proceed to next file. See Figure 4-2.

Figure 4-2 List of Markers in the File

7. Select Text Symbols from the View menu.


8. Copy the first marker name in the list and open the corresponding translated
file.
9. Select Find/Change from the Edit menu.
10. Select Marker Text: in the Find drop-down combo box.

3BSE 025 113R301 37


On-line Help Marker in English Original File Section 4 On-line Help

11. Paste the marker name to the right of the Find box. See Figure 4-3.

Figure 4-3 Find Markers

12. Press Find and check where the insertion point stops. If it is hard to see where
the insertion point is, you can zoom in before you click Find.
13. Highlight the marker and select Marker from the Special menu.
If the marker is highlighted the marker text will be seen in the Marker window.
See Figure 4-4

Figure 4-4 Marker Text in English Original File

38 3BSE 025 113R301


Section 4 On-line Help Pasting Marker Text in Translated File

4.5 Pasting Marker Text in Translated File


Paste the marker text in the translated files in the following way:
1. Open the corresponding translated file.
2. Find the same place in the translated file and position the insertion point on the
text line.
3. Check for any remaining markers and erase them, if necessary.
4. Select Marker from the Special menu and select ProgramLinkToHelpTopic
from the Marker Type: drop-down combo box.
5. Paste the marker name (from the English file) in the Marker Text: window
and press New Marker.
6. Repeat the steps above for the next marker in the list. When the list is done -
proceed with the next file until the whole translated User’s Guide is marked.
7. Then proceed with the other translated User’s Guides.

4.5.1 Processing Help Files


The On-line Help files now have to be processed in WebWorks Publisher and in
HTML Workshop. The processing of the On-line Help files in WebWorks Publisher
and HTML Workshop is described in Appendix B, On-line Help Procedure.
1. Carry out all steps in Appendix B, On-line Help Procedure.

4.5.2 Renaming On-line Help Files


When all On-line Help files have been processed:
1. Add the language abbreviation to the On-line Help file names. If the file name
for example is
work_help.chm
change the Swedish file name to
work_help_SVE.chm
SVE is the language abbreviation of Swedish. For more information on
language abbreviations, see Appendix A, Language Abbreviations etc..

3BSE 025 113R301 39


Pasting CHM Files in Process Portal File Structure Section 4 On-line Help

4.6 Pasting CHM Files in Process Portal File Structure


The CHM-files can now be pasted in the structure for testing before creating a
Extension Pack. See Section 7, Creating an Extension Pack with Translated Files.
1. Create a new sub-folder under On-line Help with the language abbreviation
(SVE for Swedish etc.). See Figure 4-5. For language abbreviation, see
Appendix A, Language Abbreviations etc..

Figure 4-5 Folder Structure for On-line Help folder

2. Paste all the renamed On-line Help files in the new folder.
3. The new folder will not contain all On-line Help files. A number of manuals
and corresponding On-line Help are still in US English and not meant to be
shown in the operator user interface.
The Regional Settings can now be selected and after that a test can be performed.
4. Stop the system by using the Configuration Wizard.
5. In the Control Panel click Regional Option and select the name of the target
language in the language code drop down combo box.
6. Restart the system.

40 3BSE 025 113R301


Section 4 On-line Help Pasting CHM Files in Process Portal File Structure

7. Check the system settings for the target language and click OK.
8. Click Apply and then OK.
9. Press Ctrl+Alt+Del and log off.
10. Change the privileges from Administrator to Operator.
11. Log on again and start Process Portal as an operator.
12. Check that the On-line Help that can be reached from the operator privileges
are in your local language and not in English. If they still are in English, check
why they are not translated.

Please note that if you log on with Administrator privileges you can reach
On-line Help that has not been translated (fall back to English).

13. When the On-line Help files are checked, an Extension Pack shall be generated
and used for upgrading an Installed System Product with the target language.
See Section 7, Creating an Extension Pack with Translated Files.

3BSE 025 113R301 41


Pasting CHM Files in Process Portal File Structure Section 4 On-line Help

42 3BSE 025 113R301


Section 5 Translating Static Resources (DLL Files) About this Section

Section 5 Translating
Static Resources (DLL Files)

5.1 About this Section


This section describes how to handle Dynamic Link Library (DLL) resource files in
the translation process. The translation of the DLL files can be carried out on a
separate computer.

5.2 Background
A resource DLL file contains, among other types of information, the text in
Dialog Boxes, Buttons and other types of messages that hold text information.
In the NLS concept for IndustrialIT, all static data containing any form of text is
stored in the runtime structure of the system product.
It is possible to copy the resource DLL files, translate them in a separate tool and
then copy them to a new folder. This separate translation tool extracts the text
information from the rest of the information in the resource DLL and presents the
text in editable form.
The resource DLL files contain, among other things, information on how the text
appears on the screen (typeface, style etc.). In some localization tools, this type of
information can be changed. It is however not advisable to make any changes of
typeface, style etc., unless necessary.

5.3 Preparations
ABB has tested RC WinTrans with good results and will recommend translation in
this tool.
Install the localization tool on the client where you are working, or on a separate
computer, depending on your preference.

3BSE 025 113R301 43


Copying DLLs from a System Product Section 5 Translating Static Resources (DLL Files)

5.4 Copying DLLs from a System Product


In this case Process Portal is used as an example of a System Product.
1. Identify the bin folder in the runtime structure of the system product,
see Figure 5-1.
2. Identify all resource DLL files in the ENU folder. There are DLL files in other
folders but they are not intended for translation. The ENU folder contains all
resource DLLs that are intended for translation.

Figure 5-1 Folder Structure

3. Copy all files from the ENU folder and paste them in a separate folder or on a
separate computer where the translation shall be performed.

44 3BSE 025 113R301


Section 5 Translating Static Resources (DLL Files) Using the Localization Tool

5.5 Using the Localization Tool


The localization tool gives you an optimized environment in which to do your
translation. It keeps track on previous translations.
In all translation work, and in particular for computers, there can be problems with
insufficient space for the translated text. This will not be a big problem when using
a localization tool. All dialog boxes and other windows are viewed in a separate
window where the translated result can be seen. For example, if the space for a
button is too small, the button shape can easily be changed to fit the text. This can
be made interactively in the program. See Figure 5-2.

Original button Translated text Stretched button


with sufficient with insufficient to accommodate
space space translated text

Figure 5-2 How to adjust the space for the text

5.5.1 Strings that must not be Translated


Please note that a few strings in some of the static DLLs must not be translated. In
Appendix A, Language Abbreviations etc. there is a list of DLL strings that must
not be translated.

3BSE 025 113R301 45


Pasting Translated DLLs to the Client File Structure for Test Section 5 Translating Static Resources

5.6 Pasting Translated DLLs to


the Client File Structure for Test
When the translation work in the localization tool is finished, you put all target files
that have been created in a folder with the same name as the abbreviation of the
language. The contents of this folder shall be copied to a similar folder in all
workstations of Process Portal.
1. On the client selected for installation and test of the localization, identify the
bin folder, see Figure 5-3. The three-letter long folder name must reflect the
target language. Appendix A, Language Abbreviations etc. contains a list of
language abbreviations.

Figure 5-3 Folder structure for bin folder

2. Paste all files that have been translated with the localization tool.
The Regional Settings can now be changed and after that a test can be performed.
3. Stop the system by using the Configuration Wizard.
4. In the Control Panel click Regional Options and select the name of the target
language in the language drop down menu box.

46 3BSE 025 113R301


Section 5 Translating Static Resources (DLL Files) Pasting Translated DLLs to the Client File

5. Check the system settings for the target language and click OK.
6. Click Apply and then OK. The language in the dialog boxes have now been
changed to the target language.
7. Start the system again.
8. Check a few of the dialog boxes etc. When the localization is completed, an
Extension Pack shall be generated and used for upgrading an Installed System
Product with the target language). See Section 7, Creating an Extension Pack
with Translated Files.

3BSE 025 113R301 47


Pasting Translated DLLs to the Client File Structure for Test Section 5 Translating Static Resources

48 3BSE 025 113R301


Section 6 Translating Workplace Windows, Faceplates etc. About this Section

Section 6 Translating Workplace Windows,


Faceplates etc.

6.1 About this Section


This section deals with the translation of Workplace Windows, Faceplates etc.
They are examples of aspect data that have to be extracted by a Translation
Handler in the Import/Export tool. When the extraction has been completed,
this type of data is stored in resource DLLs which can easily be translated in a
localization tool. These data are now called application data. For test purposes,
the application data can be loaded into the Process Portal by using the same tool as
was used for extracting.

6.2 Extracting Aspect Data


Use the following steps to extract aspect data and save them as DLLs.
1. Start the Import/Export application by selecting
Start > Programs > ABB Industrial IT > OperateIT > Process Portal A>
Import Export. The Import/Export window will now appear on the screen.
See Figure 6-1.

Figure 6-1 The Import/Export window

3BSE 025 113R301 49


Extracting Aspect Data Section 6 Translating Workplace Windows, Faceplates etc.

2. Select the Afw File that contains the aspects that are subject to translation.
3. On the menu bar - select Translations > Extract Translations. The Extract
Translations window will now appear on the screen. See Figure 6-2.

Figure 6-2 The Extract Translation window

4. Select your source language in the Language drop-down list box (English in
this example).
5. Select All layers in the Layer drop-down list box.

50 3BSE 025 113R301


Section 6 Translating Workplace Windows, Faceplates etc. Translate DLLs in the Localization Tool

6. Click the button to open the Select Translation File window.


See Figure 6-3.

Figure 6-3 The Select Translation File window

7. Select a folder where the extracted DLL file can be saved.


8. Click Save to leave the window.
9. Click OK in the Select Translation File window. The aspect data with the
selected language will now be extracted and saved as a resource DLL with the
specified path.
10. If the translation shall be performed on a separate computer,
move the DLL files.
11. Repeat the steps above for all files.

6.3 Translate DLLs in the Localization Tool


Use the same localization tool as described in section 5, see Using the Localization
Tool on page 45.

3BSE 025 113R301 51


Loading Translation into the Process Portal for Test Section 6 Translating Workplace Windows,

6.4 Loading Translation into the Process Portal for Test


When the aspect data stored as resource DLLs are translated, load the DLLs into the
Process Portal for test.
1. Start the Import/Export application by selecting
Start > Programs > ABB Industrial IT > OperateIT > Process Portal >
Import Export. The Import/Export window will now appear on the screen.
See Figure 6-4.

Figure 6-4 The Import/Export window

52 3BSE 025 113R301


Section 6 Translating Workplace Windows, Faceplates etc. Loading Translation into the Process

2. On the menu bar - select Translation > Load Translation. The Load
Translation window will now appear on the screen. See Figure 6-5.

Figure 6-5 The Load Translation window

3. Select your Target file, i.e. the translated resource DLL and click Open.
The contents of the translated DLL file will now be loaded into the
aspect directory.
The Regional Settings can now be selected and after that a test can be performed.
4. Stop the system by using the Configuration Wizard.
5. In the Control Panel click Regional Option and select the name of the target
language in the language code drop down menu box.
6. Check the system settings for the target language and click OK.
7. Click Apply and then OK. The language in dialog boxes have now been
changed to the target language.
8. Start the system again.
9. Check a few of the translated aspects. When the localization is completed, an
Extension Pack shall be generated and used for upgrading an Installed System
Product with the target language). See Section 7, Creating an Extension Pack
with Translated Files.

3BSE 025 113R301 53


Loading Translation into the Process Portal for Test Section 6 Translating Workplace Windows,

54 3BSE 025 113R301


Section 7 Creating an Extension Pack with Translated Files About this Section

Section 7 Creating an Extension Pack


with Translated Files

7.1 About this Section


This section explains how to create an Extension Pack containing the following file
types:
• On-line Documentation (SGI files)
• On-line Help (FKP files)
• Static Resource DLL files
• Application Data (Extracted Resource DLL files)

7.2 Installing Product Packager


Aspect Studio has to be installed on the computer where you shall create your
Extension Pack. If not installed, read the Aspect Studio User’s Guide and follow
the installation procedure for Aspect Studio and the Product Packager.

3BSE 025 113R301 55


Preparations before Creating an Extension Pack Section 7 Creating an Extension Pack with

7.3 Preparations before Creating an Extension Pack


1. Before an Extension Pack is created, all translated files have to be organized in
a file structure similar to the example in Figure 7-1.

Result from Section 6


Result from Section 4

Result from Section 3

Result from Section 5

Figure 7-1 File Structure for Translated Files

7.4 How to create an Extension Pack


Use the following steps to create an Extension Pack.
1. Run the AutoBuild in Aspect Studio to generate .msm files for the system
modules. For more information see $VSHFW6WXGLR8VHUV*XLGH.
2. Start the Product Packager by selecting:
Start > Program > ABB IndustrialIT > EngineerIT > Aspect Studio >
Product Packager.

56 3BSE 025 113R301


Section 7 Creating an Extension Pack with Translated Files How to create an Extension Pack

3. In the Product Packager - select the Extension Pack Wizard by selecting


Edit and then New Extension Pack. The Extension Pack Wizard will now
appear on the screen. See Figure 7-2.

Figure 7-2 The Extension Pack Wizard window

3BSE 025 113R301 57


How to create an Extension Pack Section 7 Creating an Extension Pack with Translated Files

4. Click the button to open a Product MSI Browse window. See Figure 7-3.

\
P
P
'X

Figure 7-3 The Product MSI File Browse window

5. Select the source product by selecting the corresponding PVL file.


Click 2SHQ to select the file.
Pointing out the source will eliminate the risk of installing an Extension Pack on the
wrong product.

58 3BSE 025 113R301


Section 7 Creating an Extension Pack with Translated Files How to create an Extension Pack

6. Click on Next to move to the second window. The second Extension Pack
Wizard window will now appear on the screen. See Figure 7-4.

Figure 7-4 The second Extension Pack Wizard window

7. The 1DPH text box will be automatically filled in. You can however change the
name if necessary. In the Owner text box, fill in your name. Then click 1H[W.
If you want to change what you entered on the previous dialog(s), click %DFN.
8. The third window will now appear on the screen. See Figure 7-5.

Figure 7-5 The third Extension Pack Wizard window

3BSE 025 113R301 59


How to create an Extension Pack Section 7 Creating an Extension Pack with Translated Files

9. Type the path to the location where you want to save the Extension Pack,
or Click the button to open the Service Pack File Browse window.
See Figure 7-6. The Service Pack and Extension Pack tools are utilizing the
same browse window.

Figure 7-6 The Service Pack File Browse window

60 3BSE 025 113R301


Section 7 Creating an Extension Pack with Translated Files How to create an Extension Pack

10. Select the [PO file where the Extension Pack shall be saved and click 6DYH.
The third Extension Pack Wizard will now appear on the screen again.
See Figure 7-7.

Figure 7-7 The third Extension Pack Wizard window

11. Click )LQLVK to exit the Extension Pack Wizard.


The Extension Pack is now ready and will be part of a Creation of a Product
Distribution Package. For more information see $VSHFW6WXGLR8VHU¶V*XLGH.

3BSE 025 113R301 61


How to create an Extension Pack Section 7 Creating an Extension Pack with Translated Files

62 3BSE 025 113R301


Appendix A Language Abbreviations etc. Language and Associated Abbreviations

Appendix A Language Abbreviations etc.

A.1 Language and Associated Abbreviations


This table contains a code for each language (local) that shall be used in the target
DLLs and as name on the folder holding translated DLLs. The table shows a list of
some languages and their corresponding codes. A complete list can be found on
Microsoft Home page: http//nsdn.microsoft.com/............

Abbreviation
Language Note
(Code)
Belgian (Flemish) NLB Latin 1
Czech CSY Latin 2
Danish DAN Latin 1
Dutch (Standard) NLD Latin 1
English (American) ENU Latin 1
English (Australian) ENA Latin 1
English (British) ENG Latin 1
English (Canadian) ENC Latin 1
English (Ireland) ENI Latin 1
English (New Zealand) ENZ Latin 1
Finnish FIN Latin 1
French (Belgian) FRB Latin 1
French (Canadian) FRC Latin 1
French (Standard) FRA Latin 1

3BSE 025 113R301 63


Language and Associated Abbreviations Appendix A Language Abbreviations etc.

Abbreviation
Language Note
(Code)
French (Swiss) FRS Latin 1
German (Austrian) DEA Latin 1
German (Standard) DEU Latin 1
German (Swiss) DES Latin 1
Greek ELL Other
Hungarian HUN Latin 2
Icelandic ISL Latin 1
Italian (Standard) ITA Latin 1
Italian (Swiss) ITS Latin 1
Norwegian (Bokmal) NOR Latin 1
Norwegian (Nynorsk) NON Latin 1
Polish PLK Latin 2
Portuguese (Brazilian) PTB Latin 1
Portuguese (Standard) PTG Latin 1
Russian RUS Cyrillic
Slovak SKY Latin 2
Spanish (Mexican) ESM Latin 1
Spanish (Modern) ESN Latin 1
Spanish (Standard/Traditional) ESP Latin 1
Swedish SVE Latin 1
Turkish TRK Latin 2

64 3BSE 025 113R301


Appendix A Language Abbreviations etc. Restrictions in Translation of some DLL Strings

A.2 Restrictions in Translation of some DLL Strings


The table below contains DLLs with some strings that must not be translated.

'//1DPH 5HVRXUFH,G 6WULQJ


AdvAeListConfigurationCtrl_ENU.dll 204 IDS_FILTER only (*.wav)|*.wav||
AdvAeListConfigurationCtrl_ENU.dll 206 IDS_DEF_FILTER
AdvAeListConfigurationCtrl_ENU.dll 225 IDS_MEDIA_DIR
AdvAeListConfigurationCtrl_ENU.dll 226 IDS_WINDIR_ENV_VARIABLE
AfwCommonDialogs.dll 104 *Generic Type
AfwCWSecurityConfig(_ENU).dll 131 IndustrialITOperator
AfwCWSecurityConfig(_ENU).dll 132 IndustrialITApplication Engineer
AfwCWSecurityConfig(_ENU).dll 133 IndustrialITSystem Engineer
AfwSecurityInit_ENU.dll 101 IndustrialITSvr
AfwSecurityInit_ENU.dll 102 IndustrialITAdmin
AfwSecurityInit_ENU.dll 103 IndustrialITUser
AfwWebPanel_ENU.dll 114 Tool View
AfwWebWorkplace_ENU.dll 109 Tool View
AfwVhnInternalComponents_ENU.dll 104 Tool View
AfwVhnSupport_ENU.dll 103 Tool View
AfwVhnSupport_ENU.dll 104 Menu View
AfwVhnSupport_ENU.dll 105 Bar View
AfwVhnSupport_ENU.dll 106 Web View
AfwWorkplaceApplication_ENU.dll 101 Tool View
AfwWorkplaceLogin_ENU.dll 101 Tool View
HtTrendTemplate_ENU.dll 230 IDS_COLUMN_VISIBLE
HtTrendTemplate_ENU.dll 231 IDS_COLUMN_STATUS

3BSE 025 113R301 65


Restrictions in Translation of some DLL Strings Appendix A Language Abbreviations etc.

'//1DPH 5HVRXUFH,G 6WULQJ


HtTrendTemplate_ENU.dll 231 IDC_EDITWIDTH
HtTrendTemplate_ENU.dll 232 IDS_COLUMN_COLOR
HtTrendTemplate_ENU.dll 232 IDC_SPIN_WIDTH
HtTrendTemplate_ENU.dll 233 IDS_COLUMN_ICON
HtTrendTemplate_ENU.dll 234 IDS_COLUMN_NAME
HtTrendTemplate_ENU.dll 235 IDS_COLUMN_DESCRIPTION
HtTrendTemplate_ENU.dll 236 IDS_COLUMN_ASPECT
HtTrendTemplate_ENU.dll 237 IDS_COLUMN_PROPERTY
HtTrendTemplate_ENU.dll 238 IDS_COLUMN_LOG
HtTrendTemplate_ENU.dll 239 IDS_COLUMN_CURVAL
HtTrendTemplate_ENU.dll 240 IDS_COLUMN_LOWRANGE
HtTrendTemplate_ENU.dll 241 IDS_COLUMN_HIGHRANGE
HtTrendTemplate_ENU.dll 242 IDS_COLUMN_OFFSET
HtTrendTemplate_ENU.dll 243 IDS_COLUMN_FILTER
HtTrendTemplate_ENU.dll 244 IDS_COLUMN_STYLE
HtTrendTemplate_ENU.dll 245 IDS_COLUMN_RULERTIME
HtTrendTemplate_ENU.dll 246 IDS_COLUMN_RULERVAL
HtTrendTemplate_ENU.dll 247 IDS_COLUMN_TREATMENT
HtTrendTemplate_ENU.dll 248 IDS_COLUMN_MEANVAL
HtTrendTemplate_ENU.dll 249 IDS_COLUMN_EXTRAPOLATE
HtTrendTemplate_ENU.dll 250 IDS_COLUMN_MINVAL
HtTrendTemplate_ENU.dll 251 IDS_COLUMN_MAXVAL
HtTrendTemplate_ENU.dll 252 IDS_COLUMN_PAIR

66 3BSE 025 113R301


Appendix B On-line Help Procedure To work with WebWorkPublisher and HTML Workshop

Appendix B On-line Help Procedure

B.1 To work with WebWorkPublisher and HTML Workshop


Before you start making On-line help, make a copy of the approved print file in a
new folder. Also put the _help.h files here for later use.
1. Open the book file in Frame Maker 6.0. Set Conditional Text in section 1 to
On-line Help Only and import the format into the rest of the book. Special Æ
Conditional Text Æ ShowÆ On-line Help Only, Click Set.
2. Select the book, File Æ Import Æ Format, mark the variable box and click
Import.
3. Open the TOC-file. SpecialÆ Delete pages ii Æ last page, File Æ Generate
Update. Don’t insert Contents Continued, leave it. You don’t have to worry
about page breaking in On-line Help.
4. Stretch pictures in every section, mostly down and to the right.
5. When the book is prepared for On-line Help, Generate and Save.
a. Open Frame Maker 6.0, and choose File Æ Print SetUp Æ Letter.
Have both versions minimized.
b. Open up WebWork Publisher from the Start menu. Quadralay Æ
WWP.
6. Choose Template: ABB HTML HELP, Click OK.
7. Choose Project Name: for example Admin1_1, click Next
8. Use Browse button and select the file (.book) prepared for On-line Help
(On Desktop if you put it there), click Open, Next, Next.
9. Next display: mark the Convert Later alternative, click Finish.
10. Delete cover files (pdfcoverFront, fcover….) from the book in the next step.
Select it, Project Æ Delete Files, click OK. Make sure TOC is the first part in
the book and IX the last one.

3BSE 025 113R301 67


To work with WebWorkPublisher and HTML Workshop Appendix B On-line Help Procedure

11. Go to Options, Change the Output file by using Browse. Program files Æ
Quadralay Æ WWP Æ Projects Æ Admin1_1 (ex) (Do not mark a specific
file, just click OK)
12. Go to the Project Menu, Choose Generate All.
13. Go to the Files tab.
14. Check the chm-file. If it is not OK, make the corrections in FrameMaker, and
start all over with WWP.
15. If the chm is OK, save and go on to the next step. Close WWP.
a. Open Program Files Æ Quadralay Æ WWP Æ Projects Æ
Admin (for ex) .hhp. Double Click on the hhp- file and HTML Workshop
opens up. If it does not, open HTML Workshop from the Start menu and
open it from the file menu.
16. Find MAP and double click on it. Remove the two files that are already there
by selecting them one at a time and click Remove.
17. Click on the Header File button. Browse to help.p on Desktop.
Open Æ OK and click Save the Project.
18. Print the help.p file.
19. Go to Contents - all sections with or without a “book” should have another
symbol. Mark the section Æ go to the pen Æ Advanced Æ Image Index = 2,
click OK. Do this step for every Book, Section and Appendix.
a. Go to the File menu Æ Compile. Use the Browse button: Quadralay Æ
WWP Æ Admin (ex) .hhp, Click Open and mark the check box: Save
all files… Then click Compile.
b. Go to Test in the menu, select HTML Help AI, Browse: Quadralay Æ
WWP Æ Admin (ex) – chm-file. Make a copy of the chm file on
Desktop.
c. Command: Help Context
HTML file map number: check the printed help.p file and test the numbers.
For example: 0x7001. Test.

68 3BSE 025 113R301


INDEX

A P
Acrobat Setup window 29 PDF files (Portable Document Format) 29
Anchors 28 Privileges 24

C R
Cross-references in documents 28 Resource DLL 43

D T
Direction of text 20 Table formats 28
DLL (Dynamic Link Library) 43 Target language 9
Text direction 20
F
Figure formats 28 U
Unicode 20
H
Help button identity 36 W
Help text markers 36 Windows 19

I
Insufficient text space 45

L
Local language 9

M
Microsoft GUI Guide 28

O
On-line Help 33
On-line Manuals 27

3BSE 025 113R301 69


,QGH[

70 3BSE 025 113R301


3BSE 025 113R301. Printed in Sweden June 2002
Copyright © 2001-2002 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.

http://www.abb.com/control

Automation Technology Products Automation Technology Products Automation Technology Products


Västerås, Sweden Wickliffe, Ohio, USA Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: processautomation@se.abb.com email: industrialitsolutions@us.abb.com email: marketing.control-prodcts@de.abb.com

You might also like