Introduction to domino_global_workbench_8.5

®

IBM Software Group

© IBM Corporation

Introduction of Domino Global WorkBench 8.5

Xiao Feng Ji: [email protected] Ling Xu: [email protected]

IBM Lotus Notes/Domino Globalization Team

IBM Software Group | Lotus software

1. Domino Global Workbench 8.5 Overview

2. Template Localization Process and Tasks

3. Steps to Localize Templates with DGW 8.5 Glossary Version

4. Steps to Localize Templates with DGW 8.5 Properties Version

Agenda

2




3. Steps to Localize Templates with DGW 8.5 Glossary version

4. Steps to Localize Templates with DGW 8.5 Properties version

Agenda

3


Domino Global Workbench 8.5 Overview

1. Overview of Domino Global WorkBench 8.5

2. Components of A DGW “Project”

3. Things DGW Does

4. Key Definitions in A DGW Project

5. Features of A DGW Glossary Database

6. Multilingual Support

7. Advantages of Using DGW

4


1. Overview of Domino Global WorkBench 8.5

• Domino Global WorkBench (DGW) 8.5 is a set of software tools which can

help you perform the localization (translation) of Domino applications.

• It automatically extracts terms from your application and stores them in

glossaries or properties which are ready for translation.

• It builds localized versions of applications automatically using the

translated glossaries or properties files.

5


The Footprint of Domino Global Workbench

6


2. Components of A DGW “Project”

• The application(s) to localize.

• One or more glossary databases.

• A tag database for each source application, which provides a link

between the text in the source application(s) and the glossary entries.

• One or more built language applications generated from each source

application. These are localized applications that people will use.

7


3. Things DGW Does

• Creates tag databases from their respective source applications.

• Builds localized language applications from the tag databases and their

associated glossaries.

• Updates the tag database, the glossaries, and the language applications if

the design of the source application changed.

• Logs process messages to a log console and optionally to a report

database.

8


4. Key Definitions in A DGW Project

• Source application

– The application that will be localized.

• Tag database

– An intermediary database whose design elements have been tagged. This database will be used to generate language applications.

• Language application

– The application whose design elements have been translated into any language requested by the developer. The language application can be unilingual - one language per application - or multilingual - several languages per application.

• Tag

– The process of creating tagged design elements.

9


4. Key Definitions in A DGW Project (Cont’d)

• Glossary

A Domino Global WorkBench glossary is a Domino database (.NSF file).

10


4. Key Definitions in A DGW Project (Cont’d)

A glossary contains:

1. A term definition document for each piece of text.

2. Translation documents associated with each term definition document. These are where translators enter translations.

3. A glossary information document. This lists the active languages and the term types supported by the glossary. It optionally includes a description for the glossary.

4. A locale information document for each language that can be supported by the glossary.

5. Views that enable the contents of the glossary to be displayed in different ways.

6. Agents to carry out management tasks, such as importing and exporting.

11


5. Features of A DGW Glossary Database

• Context Information Support and Handling

• Do Not Translate (DNT) Terms

• Approve Flag

• Mark As Translated/Untranslated

• Word Count

• Pseudo Translation

• Import from/Export to the XLIFF File Format

12


6. Multilingual Support

• What’s a Multilingual application?

– A multilingual application is one in which the same code is used in the back-end, but the front-end can have any one of a set of translated user interfaces (that is, a multilingual application provides a single back-end, but multiple front-end interfaces).

• One of the features of Domino Global WorkBench is its ability to build “multilingual” application.

– In a multilingual application, the design elements are presented in several different languages. Each user sees the user interface, in whatever language he or she prefers and can switch from one language to another by changing the language setting in Notes or their Web browser.

13


6. Multilingual Support (Cont’d)

• A snapshot of a multilingual application

14


6. Multilingual Support (Cont’d)

• You need to ensure that your “notes.ini” file (Program Files\Lotus\Notes) has the following entry to enable the multilingual template building option in DGW.

DGWBuildMergeCompatible=1

15


7. Advantages of Using DGW

• Re-use of technical upfront investment

• Efficient use of resources

• Translation done with fully contextual information

• Re-usability of translations

• Multilingual applications

16




3. Steps to Localize Templates with DGW8.5 Glossary Version

4. Steps to Localize Templates with DGW8.5 Glossary Version

Agenda

17


Template Localization Process

18


Template Localization Tasks - Localization Analysis

• This is a job for an experienced template engineer. The following tasks

should be carried out, and any problems should be reported to the

developers of the application:

1.Check that the application supports the display of fonts and characters

needed by the target languages (for example accented characters and Asian

character sets).

2.Check that the application is ready for processing by Domino Global

WorkBench, in particular that aliases with suitable identifying prefixes have

been used. Strictly speaking, this is not essential, but will save a lot of work

later on.

3.Check translatability. Look for potential translation problems such as

impossible concatenations, use of graphics and text, splitting of sentences,

buttons with text that are too small to allow translation, table columns that are

too narrow, the use of internationally unsuitable fonts, and so on.

LA TranslationPreparation

Tag Translation Building QA

19


Template Localization Tasks - Tag

• This is a job for an template engineer, ideally one of the developers of the application. The following WorkBench tasks should be carried out:

1. Tag the application. This connects the application with a glossary/properties and makes new glossary entries or new property files where necessary.

2. Mark glossary entries or properties terms that must not be translated (called DNTs, “Do Not Translate”). Text which is never seen by users, or which for functionality reasons must remain untranslataed in the source language, should be marked as “Do Not Translate”.

3. Run test builds using a pseudo-language. A pseudo-language is a jumbled and expanded version of the source language. It allows the effects of translation to be examined before any real translation is done.

4. Check the test builds and report problems that arise from the design of the source to the appropriate developers.



20


Template Localization Tasks - Translation Preparation

• A template engineer should review the contents of the glossaries or terms

in properties, especially the DNT information, and provide translation

comments to give further context to translators (for example, explain how

formula and concatenations work; indicate whether a piece of text is a box

title or a button label).

• The translation specialists should look at the glossaries/properties from a

translator's standpoint and try to make his or her work as simple as

possible. A translation guideline would be helpful.



21


Template Localization Tasks - Translation• The translators translate the entries in the glossaries/properties. If the

previous tasks have been carried out, the translators will have much less

work to do.

• The translators should be experienced in translating computer software

and they should be conversant with Notes and its terminology.



22


Template Localization Tasks - Building and Checking

• Once the build process has been perfected by test building (above),

building the real language versions of the application should be

straightforward.

• However, it will be necessary for the translators to check that no source

language text remains visible in the built versions.



23


Template Localization Tasks - Quality assurance• Finally, the localized application should be tested. A quality assurance

engineer should have sound technical knowledge of Notes and standard

Web browsers.

• It will help if a test script is developed early in the localization process so

that it can be applied to all built applications later.



24






Agenda

25


Previous (English)

template

Updated

Glossary DBUpdated Tag DB

Previous Tag DB

German template

French template

Taiwanese template

Previous

German template

Previous

French template

Previous

Taiwanese template

Original (English)

template

DGW

Language Templates

Glossary DB

DGW

Translation Language

Glossary DB

Updated Tag DB

Preprocessing Translation Post-processing

1

2

3 4

5

Extract Term from Design

Note

Extract Term into Notes document

Send translation package to Translation

companies

Receive translation and compile into

Language templates

Template Localization Process using Glossary

26


Steps to localize templates with DGW8.5 glossary version

1. Install Domino Global WorkBench 8.5

2. Create a glossary database

3. Create a tag file and update glossary database with DGW 8.5

4. Mark the DNT terms in glossary file

5. Send the glossary to translate

6. Create the language template with translated glossary files

7. Run test cases for creating language application

27


Step 1 – Install Domino Global WorkBench 8.5

1. Install DGW 8.5 glossary version step by step.

Install

Glossary

Tag

DNT

Translate

Build

Test

28


Step 1 – Install Domino Global WorkBench 8.5 (Cont’d)

2. Launch DGW 8.5 Glossary version.

Install

Glossary

Tag

DNT

Translate

Build

Test

29


Step 2 – Create a glossary database• Create a glossary database with the standard DGW glossary template file

via Notes Client;

Note: The glossary template location is in Notes Data folder, default path is C:\Program Files\IBM\Lotus\Notes\Data

Install

Glossary

Tag

DNT

Translate

Build

Test

30


Step 3 – Create a tag file and update glossary database

1. Create a project and name your project;

Install

Glossary

Tag

DNT

Translate

Build

Test

31


Step 3 – Create a tag file and update glossary database (Cont’d)

2. Import a source application into the project;

Install

Glossary

Tag

DNT

Translate

Build

Test

32


3. Import a glossary file into the project;

Install

Glossary

Tag

DNT

Translate

Build

Test


33


4. Name your tag file and set tagging options;

Install

Glossary

Tag

DNT

Translate

Build

Test


34


5. Some important tagging options settings;

After the tagging process, your glossary will be updated. This means that all the terms which are not found in old glossary will be updated in glossary.

Install

Glossary

Tag

DNT

Translate

Build

Test


35


Step 4 – Mark DNT terms in glossary file

1. Go to the default “All terms and translation ”view in glossary;

Install

Glossary

Tag

DNT

Translate

Build

Test

36


Step 4 – Mark DNT terms in glossary file (Cont’d)

2. Select one term and mark the “Do Not Translate” if this term is not translatable.

Install

Glossary

Tag

DNT

Translate

Build

Test

37


Step 5 – Send the glossary to translate

• Send the glossary files to translators, and they can go to “Untranslated terms” view to search and translate the untranslated terms.

Install

Glossary

Tag

DNT

Translate

Build

Test

38


Step 6 – Create the language applications with translated glossary files

1. Click the “Choose Language” button and select the language for the target application;

Install

Glossary

Tag

DNT

Translate

Build

Test

39


Step 6 – Create the language applications with translated glossary files (Cont’d)

2. Name your language application;

Install

Glossary

Tag

DNT

Translate

Build

Test

40



3. Set the “Errors/Warning Level” for building process.

Usually, we will deselect “Translation not approved”.

Install

Glossary

Tag

DNT

Translate

Build

Test

41



4. Some other options. The first three options should be selected.

If you need to export the log report to a database, you can locate a file for DGW to do that.

Install

Glossary

Tag

DNT

Translate

Build

Test

42


Step 7 – Testing

• Finally, you have to run necessary testing on your created language application.

From our years’ of template globalization and localization experiences, most of the functional defects are caused by “over-translating”.

• The tests should cover most of the functional areas in your application, especially for the design elements which need to be translated; A good design at the early stage could save lots of time and efforts in the testing and bug-fixing phases.

Install

Glossary

Tag

DNT

Translate

Build

Test

43






Agenda

44


New Features in DGW85 Properties Version

• DGW can now tag translatable terms into properties files instead of Notes documents in the glossary database. There will be one properties file for each design element. In addition, the tag database will not be required in the building process. For Rich Text Format (RTF) terms, they will be tagged into a special format to get translated properly.

• DGW can also store the “Do Not Translate” terms into DNT properties files. There will be only one DNT properties file for each application. Moreover, the DNT comments in the applications are also put into the DNT properties files.

• Besides, the layout information are now stored in the properties files as well. You can export the layout information from previous language applications and import it into current language applications. By doing so, the human work for adjusting the layout in language applications will be greatly reduced.

45


Template Localization Process Using Properties

DGW

Original (English)

templates

Layout.properties (extracted from language templates via DGW)

DNT.properties

Language

Templates

Language.properties

DGW

English.properties

Original (English)

templates

Translation

TM

DNT.properties

1

23

4

5

Preprocessing Translation Post-processing

Extract terms from design elements

Send translation packages to translation companies

Receive translations and compile them into language templates

46


Steps to Localize Templates Using DGW85 Properties Version

1. Install DGW85 (Domino Global Workbench 8.5);

2. Add DNT comments into your customized applications;

3. Create the English properties and DNT properties by DGW85;

4. Send the English properties to translators;

5. Build the language applications with the translated English properties (also known as “language properties”) via DGW85;

6. Perform tests on built language applications.

47


Step 1 – Install DGW85

1. Install DGW85. Please select all components (including the Properties version and the Glossary version of DGW85) and follow the instructions on the screen to complete the installation.

Install

DNT

Tag

Translate

Build

Test

48


Step 1 – Install DGW85 (Cont’d)

2. Launch “Domino Global WorkBench 8.5 – Properties”.

Install

DNT

Tag

Translate

Build

Test

49


Step 2 – Add DNT Comments into Your Customized Applications

1. Open “config.ini” in your DGW installation path, (the default path is “C:\Lotus\Dgw\DGW Properties”). The DNT tagging rules are defined in this file.

Install

DNT

Tag

Translate

Build

Test

50


2. Add DNT comments into your code.

Install

DNT

Tag

Translate

Build

Test

Step 2 – Add DNT Comments into Your Customized Applications (Cont’d)

51


Step 3 – Create the English Properties and DNT Properties by DGW85

1. Create a new project in DGW85.

Install

DNT

Tag

Translate

Build

Test

52


2. Select the source application you will localize.

Install

DNT

Tag

Translate

Build

Test

Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d)

53


3. Select a folder to store the generated properties files.

Install

DNT

Tag

Translate

Build

Test


54


4. Click the “Create Properties” button;

Install

DNT

Tag

Translate

Build

Test


55


5. Put in the name of the DNT properties to be imported. Please leave this field blank if no DNT properties are available at this time.

Install

DNT

Tag

Translate

Build

Test


56


6. Set the tagging options and begin the creation process.

Install

DNT

Tag

Translate

Build

Test


57


7. When done, the English properties and DNT properties will be placed into the folder you selected.

Install

DNT

Tag

Translate

Build

Test


58


8. The generated English properties files will be like the example below:

The ID of translatable strings is in this format: type.title.subtype.subtitle.original_string

Install

DNT

Tag

Translate

Build

Test


59


9. The generated DNT properties file will be like the example below:

Install

DNT

Tag

Translate

Build

Test


60


Step 4 – Send Out the English Properties for Translation • The English properties are now ready to be translated. You can send

them to translators and then receive translated English properties (language properties) from them.

• In order to greatly reduce the efforts required for translation and also increase the translation quality, the English properties are usually processed and managed in translation tools. There are plenty of free and proprietary translation tools available for this purpose, and you can refer to the link below for more information on them:

http://en.wikipedia.org/wiki/Computer_assisted_translation

Install

DNT

Tag

Translate

Build

Test

61


Step 5 – Build the Language Applications via DGW85

1. Select the target language.

Install

DNT

Tag

Translate

Build

Test

62


Step 5 – Build the Language Applications via DGW85 (Cont’d)

2. Select a path to put the language application.

Install

DNT

Tag

Translate

Build

Test

63



3. Set the error/warning level options.

Install

DNT

Tag

Translate

Build

Test

64



4. Set the building options.

Install

DNT

Tag

Translate

Build

Test

65



5. Begin the building process. The application will be put in the directory designated when done.

Install

DNT

Tag

Translate

Build

Test

66


Step 6 – Perform Tests on Language Applications

• To ensure the quality of the built language applications, tests should be performed to confirm that all the important functions in the English applications are also working fine in the language ones.

Install

DNT

Tag

Translate

Build

Test

67


The Layout Properties

• Currently, the DGW layout exporting function only works on the following design elements: Table Cell (with an ID), Button, Field, Embedded Outline, Picture, and Frameset. In addition, only parts of the layout settings (mainly the “width” and “height”) are extracted to be put into layout properties.

• Most of the localization layout issues are related to the length of translated strings. Therefore, exporting layout properties for the design elements mentioned above can cover most of the layout changes in language applications.

• The process is as follows:

1. Export layout properties from previous language applications;

2. Import the layout properties into current language applications.

68


The Layout Properties – Export English Layout Properties

1. To export layout properties from English applications, please check the “Export layout properties” checkbox and select the “For source database” option. Then you can begin the usual properties creation process.

69


The Layout Properties – Export English Layout Properties (Cont’d)

2. When done, the layout properties “LAOUT.properties” will be put in the same directory where the English properties are put. And the layout properties will look like the example below:

70


The Layout Properties – Export Language Layout Properties

• If you plan to export language applications’ layout properties, please select the “For language database” option and put in the path for corresponding English application.

71


The Layout Properties – Import Layout Properties

• To import the layout properties, you only need to put the layout properties into the same properties folder for that specific application.

72


Useful Information

• Where to Obtain DGW85

You can obtain a copy of DGW 8.5 from your Lotus Notes 8.5 Client product CD.

• Some useful links:

Domino Global WorkBench Forum Discussion

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=273

Helping customers globalize their IBM Lotus Notes applicationshttp://www.ibm.com/developerworks/lotus/library/notes-global-pt1/

Best practices in globalization: Developing IBM Lotus Notes applicationshttp://www.ibm.com/developerworks/lotus/library/notes-global-pt2/

73


Japanese

Hebrew

Thank YouEnglish

MerciFrench

Russian

DankeGerman

GrazieItalian

GraciasSpanishObrigado

BrazilianPortuguese

Arabic

SimplifiedChinese

TraditionalChinese

Thai

Hindi

Tamil

go raibh maith agatGaelic

Sinhala

Korean

Salamat

Tagalog

Terima KasiIndonesian and Malay

74

Introduction to domino_global_workbench_8.5

Technology

term definition

add dnt comments

template localization

current language

update glossary

domino global

previous language

dnt properties