Enhancing Worker Digital Experience: A Hands-on Workshop for Partners
Introduction to domino_global_workbench_8.5
1. Introduction of Domino Global WorkBench 8.5 Xiao Feng Ji: [email_address] Ya Ling Xu: [email_address] IBM Lotus Notes/Domino Globalization Team
2. 1. D omino Global Workbench 8.5 Overview 2. Template Localization Process and Tasks 3. Steps to L ocalize T emplates with DGW 8.5 Glossary Version 4. Steps to L ocalize T emplates with DGW 8.5 Properties Version Agenda
3. 1. D omino Global Workbench 8.5 Overview 2. Template Localization Process and Tasks 3. Steps to L ocalize T emplates with DGW 8.5 Glossary version 4. Steps to L ocalize T emplates with DGW 8.5 Properties version Agenda
17. 1. D omino Global Workbench 8.5 Overview 2. Template Localization Process and Tasks 3. Steps to L ocalize T emplates with DGW8.5 Glossary Version 4. Steps to L ocalize T emplates with DGW8.5 Glossary Version Agenda
25. 1. D omino Global Workbench 8.5 Overview 2. Template Localization Process and Tasks 3. Steps to L ocalize T emplates with DGW 8.5 Glossary Version 4. Steps to L ocalize T emplates with DGW 8.5 Properties Version Agenda
26. Previous (English) template Updated Glossary DB Updated Tag DB Previous Tag DB German template French template 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 Previous German template Previous French template Previous Taiwanese template
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44. 1. D omino Global Workbench 8.5 Overview 2. Template Localization Process and Tasks 3. Steps to L ocalize T emplates with DGW 8.5 Glossary Version 4. Steps to L ocalize T emplates with DGW 8.5 Properties Version Agenda
45.
46. 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 2 3 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
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74. Japanese Hebrew Thank You English Merci French Russian Danke German Grazie Italian Gracias Spanish Obrigado Brazilian Portuguese Arabic Simplified Chinese Traditional Chinese Thai Hindi Tamil go raibh maith agat Gaelic Sinhala Korean Salamat Tagalog Terima Kasi Indonesian and Malay
Editor's Notes
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
A Domino Global WorkBench 'project' comprises: The database(s) you want to localize. These might be new databases in the course of development, or existing databases now destined for use internationally. They are the 'source' databases. Domino Global WorkBench is primarily intended for localizing the design of a database, rather than the data documents it contains. Documents that are part of the design, such as small Help documents, can be localized using Domino Global WorkBench. Larger documents are best localized separately. One or more glossaries. These are Notes databases, built on a standard template, that hold terminology from the source database(s). Each entry in the glossary has one or more translation documents associated with it. Translators translate the text in the translation documents. For each source database a tagged database, which provides a link between the text in the source database(s) and the glossary entries. For each source database, one or more built language databases. These are the localized databases that people will use. Typically they comprise a multilingual Web site. There are two types of language database: A standard database (or template), with its design elements localized in one language. This is termed a 'unilingual' database. A multilingual database (or template), with its design elements localized in several languages. Users can switch from one language to another from Notes or from their Web browser. Language synchronization features can be added to the language databases to support translation workflow. Entries in a projects database, which stores information about Domino Global WorkBench projects. (Optional) Records of WorkBench operations stored in a reports database.
Demo: Show what a glossary database looks like.
Demo: Show an English template and a language template.
Demo: Show “config.ini”.
Domino Global WorkBench provides a number of advantages over conventional localization methods, including: Re-use of technical up-front investment One technical person can do the initial analysis of the application, define what needs to be translated and what should be left in the source language, provide contextual comments for translators, and so on. This effort speeds the work of all translators, who do not have to concern themselves with, for example, what should and what should not be translated (in fact much text that should not be translated they do not even see). Efficient use of resources Technical people perform technical tasks, whereas translators concentrate on translation. Translation is done with full contextual information Translators know at all times what design element they are translating and they can always trace it back in the source application. Re-usability of translations Your translation investment is protected. Because all translations are stored in glossary databases with full contextual information, they can be re-used in other applications that use similar terminology. Multilingual applications You can build several translated databases from a single source, or you can build one multilingual database with design elements in several languages. This simplifies the creation of multilingual Web sites.
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
The concept to localize a Notes application is quite simple. DGW pulls all the translatable strings from a Notes application to a Notes DB which is called ‘Glossary’. Translator can append the translation for different languages on the English (base language) strings. Then , DGW builds language the application base on the translation in the glossary. After testing and fine-tuning on the language application, Notes application localization is done. Following chart describes the localization process. We will introduce how to do the Notes application localization and the best practice for each phase in below sections. However, the step by step instructions are included because that they have been in DGW help files already.
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
Page
Demo: Create tag databases, glossary databases, and mark DNT.
Demo: Create language templates.
To replace the title / subtitle with your own: Click on the title block -> select all the text by pressing Ctrl+A -> press Delete key -> type your own text
Extract terms from design notes by DGW. Translatable English properties and DNT properties are generated. Send out the English properties to translation companies. Put in the language properties, DNT properties, layout properties (extracted from the previous version of language templates), and English templates to build language templates via DGW.
Introduce the steps to localize templates with DGW85 properties version.
Demo: Create properties files and DNT properties files.