Introduction to domino_global_workbench_8.5
Upcoming SlideShare
Loading in...5
×
 

Introduction to domino_global_workbench_8.5

on

  • 4,363 views

 

Statistics

Views

Total Views
4,363
Views on SlideShare
2,376
Embed Views
1,987

Actions

Likes
0
Downloads
13
Comments
0

2 Embeds 1,987

http://www-10.lotus.com 1977
http://wiki1.swg.usma.ibm.com 10

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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.
  • Demo: Build language applications.
  • Demo: Create layout properties.

Introduction to domino_global_workbench_8.5 Introduction to domino_global_workbench_8.5 Presentation Transcript

  • Introduction of Domino Global WorkBench 8.5 Xiao Feng Ji: [email_address] Ya Ling Xu: [email_address] IBM Lotus Notes/Domino Globalization Team
  • 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
  • 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
  • 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
  • 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 .
    • I t builds localized versions of applications automatically using the translated glossaries or properties files.
  • The Footprint of Domino Global Workbench
  • 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.
  • 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.
  • 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.
  • 4. Key Definitions in A DGW Project (Cont’d)
    • Glossary
    • A Domino Global WorkBench glossary is a Domino database (.NSF file).
  • 4. Key Definitions in A DGW Project (Cont’d)
    • A glossary contains:
    • A term definition document for each piece of text.
    • Translation documents associated with each term definition document. These are where translators enter translations.
    • 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.
    • A locale information document for each language that can be supported by the glossary.
    • Views that enable the contents of the glossary to be displayed in different ways.
    • Agents to carry out management tasks, such as importing and exporting.
  • 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
  • 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.
  • 6. Multilingual Support (Cont’d)
    • A snapshot of a multilingual application
  • 6. Multilingual Support (Cont’d)
    • You need to ensure that your “notes.ini” file (Program FilesLotusNotes) has the following entry to enable the multilingual template building option in DGW.
    • DGWBuildMergeCompatible=1
  • 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
  • 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
  • Template Localization Process
  • 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:
      • Check that the application supports the display of fonts and characters needed by the target languages (for example accented characters and Asian character sets).
      • 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.
      • 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 Translation Preparation Tag Translation Building QA
  • 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:
      • Tag the application. This connects the application with a glossary/properties and makes new glossary entries or new property files where necessary.
      • 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”.
      • 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.
      • Check the test builds and report problems that arise from the design of the source to the appropriate developers.
    LA Translation Preparation Tag Translation Building QA
  • 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.
    LA Translation Preparation Tag Translation Building QA
  • 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.
    LA Translation Preparation Tag Translation Building QA
  • 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.
    LA Translation Preparation Tag Translation Building QA
  • 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.
    LA Translation Preparation Tag Translation Building QA
  • 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
  • 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
  • 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
  • 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
  • Step 1 – Install Domino Global WorkBench 8.5 (Cont’d)
    • 2. Launch DGW 8.5 Glossary version.
    Install Glossary Tag DNT Translate Build Test
  • 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 FilesIBMLotusNotesData
    Install Glossary Tag DNT Translate Build Test
  • 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
  • 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
    • 3. Import a glossary file into the project;
    Install Glossary Tag DNT Translate Build Test Step 3 – Create a tag file and update glossary database (Cont’d)
    • 4. Name your tag file and set tagging options;
    Install Glossary Tag DNT Translate Build Test Step 3 – Create a tag file and update glossary database (Cont’d)
    • 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 Step 3 – Create a tag file and update glossary database (Cont’d)
  • 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
  • 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
  • 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
  • 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
  • Step 6 – Create the language applications with translated glossary files (Cont’d)
    • 2. Name your language application;
    Install Glossary Tag DNT Translate Build Test
  • Step 6 – Create the language applications with translated glossary files (Cont’d)
    • 3. Set the “Errors/Warning Level” for building process.
    • Usually, we will deselect “Translation not approved”.
    Install Glossary Tag DNT Translate Build Test
  • Step 6 – Create the language applications with translated glossary files (Cont’d)
    • 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
  • 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
  • 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
  • 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.
  • 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
  • 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.
  • 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
  • Step 1 – Install DGW85 (Cont’d)
    • 2. Launch “Domino Global WorkBench 8.5 – Properties”.
    Install DNT Tag Translate Build Test
  • Step 2 – Add DNT Comments into Your Customized Applications
    • 1. Open “config.ini” in your DGW installation path, (the default path is “C:LotusDgwDGW Properties”). The DNT tagging rules are defined in this file.
    Install DNT Tag Translate Build Test
    • 2. Add DNT comments into your code.
    Step 2 – Add DNT Comments into Your Customized Applications (Cont’d) Install DNT Tag Translate Build Test
  • Step 3 – Create the English Properties and DNT Properties by DGW85
    • 1. Create a new project in DGW85.
    Install DNT Tag Translate Build Test
    • 2. Select the source application you will localize.
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 3. Select a folder to store the generated properties files.
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 4. Click the “Create Properties” button;
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 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.
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 6. Set the tagging options and begin the creation process.
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 7. When done, the English properties and DNT properties will be placed into the folder you selected.
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 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
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
    • 9. The generated DNT properties file will be like the example below:
    Step 3 – Create the English Properties and DNT Properties by DGW85 (Cont’d) Install DNT Tag Translate Build Test
  • 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
  • Step 5 – Build the Language Applications via DGW85
    • 1. Select the target language.
    Install DNT Tag Translate Build Test
  • 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
  • Step 5 – Build the Language Applications via DGW85 (Cont’d)
    • 3. Set the error/warning level options.
    Install DNT Tag Translate Build Test
  • Step 5 – Build the Language Applications via DGW85 (Cont’d)
    • 4. Set the building options.
    Install DNT Tag Translate Build Test
  • Step 5 – Build the Language Applications via DGW85 (Cont’d)
    • 5. Begin the building process. The application will be put in the directory designated when done.
    Install DNT Tag Translate Build Test
  • 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
  • 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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 applications http://www.ibm.com/developerworks/lotus/library/notes-global-pt1/
    • Best practices in globalization: Developing IBM Lotus Notes applications http://www.ibm.com/developerworks/lotus/library/notes-global-pt2/
  • 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