iSeries home   |   Easy400     |   CGIDEV2  
Public source
 
Introduction
Start a translation
Perform a translation
Work with a directory
Translations
Save files
A few commands
Appendix A
 
Download
 
 

 
BABEL_I
Work with translation dictionary save files
 

1. The translation dictionary

The translation dictionary is the hearth of BABEL_I. Every time you translate some text of an HTML stream file, a translation entry for that file is added to the translation dictionary, database file BABEL_IDTA/XLTDCT. In this way, when - because of some maintenance - you have to redo that translation, the translation tool feeds back all the translations that match the current texts and your translation task can be carried out in a few seconds at no risk.
The more you translate, the more you benefit from this dictionary, even for new translations. If a text string was not yet translated for the current stream file, it may have been previously translated for another stream file, and BABEL_I will fetch it back to you.
A translation dictionary with 1,000 records takes about 5Mb of disk storage.
Utilities are available to save and to restore sections of the translation dictionary (see below).

2. Work with dictionary

Figure 18 - Work with translation dictionary
Take option 4 of the home page menu (see Figure 1 on page 2). The screen in Figure 18 is displayed.
Figure 19 - Table of contents
  • Click the first radio button in Figure 18 to display the table of contens of the translation dictionary (Figure 19). Each row in the table is a summmary of the dictionary entries for the translation of an HTML stream file to another national language.
  • Click the second radio button in Figure 18 if you have to fix translation entries (see Appendix A).
  • Click the third radio button in Figure 18 to start working with translation dictionary save files (See Figure 20 when no save files exist, Figure 21 when some save files already exist).
Figure 20 - No save files
Figure 21 - Some save files

3. Translation dictionary save files

Sections of the translation dictionary can be saved to stream files called "translation dictionary save files".
These save files may contain translation entries related
  • to a single translation (from a given HTML stream file to another "target" national language), OR
  • to a group of translations identified by a generic HTML stream file name, a source language and a "target" national language.
Translation dictionary entries saved to these save files are in a more compact format, thus using much less space than the original ones in the online database dictionary.
Dictionary entries saved to these save files may be removed from the dictionary, thus reducing the disk space used by the online dictionary.
Dictionary save stream files can be easily stored to offline media.
Dictionary save file entries can be easily restored to the online dictionary when retranslation is needed because of some change in the original HTML stream files.

4. Performing the saves

To perform a dictionary save, press the button "make it now" from the screen in Figure 20 or Figure 21. A "Save translation dictionary entries (SAVDCT)" command is displayed (see Figure 22).
Figure 22 - Command SAVDCT
  • Referenced HTML file(s) (REFHTMLF) - Path of HTML stream file(s) that did undergo translation to one or more national languages. The command saves the translation entries related to the stream files in this path.
    Examples: suppose that you used BABEL_I to translate from English language to French language your application "Application 1" and that its HTML English language stream files are located in IFS directory /application1/html/english.
    If you specify:
    • REFHTMLF('/application1/html/english/intro.html'), only the translation dictionary entries related to this HTML stream file are saved.
    • REFHTMLF('/application1/html/english/*'), the translation dictionary entries related to all the HTML stream files in this generic path are saved.
    • REFHTMLF(*ALL), the translation dictionary entries related to any HTML stream file are saved.
  • To save file (SAVF) - The name of the stream file receiving the saved translation entries.
    Example: /tmp/Application1_TranslationData.txt.
    • If this save file does not exist, it is automatically created.
    • If this save file already exists, you must specify CLEAR(*YES) to have it cleared before receiving the saved entries.
  • From national language(s) (FRMLNG) - A three characters identifier of the language used in the REFHTMLF file(s). Only the dictionary entries with this "source" national language are saved.
    If you specify *ALL, dictionary entries with whatever "source" national language are saved.
  • To national language(s) (FRMLNG) - Up to 10 three characters identifiers of the "target" national languages eligible for save.
    If you specify *ALL, dictionary entries with whatever "target" national language are saved.
  • Clear save file (CLEAR) - If the save file already exists and you want to save dictionary entries there, you must specify CLEAR(*YES) to clear the save file before performimg the save.
    If you specify CLEAR(*NO) and the save file already exists, you receive an error message.
  • Remove saved entries (RMV) - Whether the saved dictionary entries should be removed from the online database dictionary after having been saved.
    Removed dictionary entries can be later on restored with command RSTDCT.

6. Work with save files

This topic deals with the operations that you can perform once you have created some "translation dictionary" save files.
Figure 23 - Contents of a single save file
Figure 24 - Contents of a multiple save file

If you have at least one save file, if you hit the radio button "save files" in the screen of Figure 18, you receive a list of the existing save files (see Figure 21).
If then you select a save file by pressing the radio button in front of it, you are displayed the table of contents of the save file. You may have two cases: either the save file contains dictionary entries related to a single translation (Figure 23), or it contains entries related to multiple translations (Figure 24).

From this screens you can do the following:

  • Restore one piece or the whole save file to the translation dictionary (see the next topic)
  • Rerun one piece or the whole save operation (provided that those entries were not removed in the previous save)
  • Delete the save file. Confirmation is requested.

7. Restore a save file

When in Figure 23 or Figure 24 you ask to restore a translation dictionary save file or a section of it, you receive the RSTDCT command screen (see the example in Figure 25) with the appropriate parameters for performing the restore operation.
  • Save file (SAVF) - Name of the dictionary save file containing the dictionary entries that you want to restore
  • Referenced HTML file(s) (REFHTMLF) - One of the following:
    • The name of the HTML stream file referenced from the saved dictionary entries that you want to restore
    • A generic* HTML stream file name, to restore all the dictionary entries referenced by the HTML stream files matching this generic name
    • *ALL, to restore all the dictionary entries in the save file.
  • Translation "from" language (FRMLNG):
    • A three characters national language identifier, to restore only the entries related to this "before translation" national language, OR
    • *ALL, to restore entries of whatever "before translation" national language
  • Translation "to" language (TOLNG):
    • A three characters national language identifier, to restore only the entries related to this "after translation" national language, OR
    • *ALL, to restore entries of whatever "after translation" national language
  • Restore option (RSTOPT) - Enter
    • *OLD, to restore only entries already existing in the translation dictionary
    • *NEW, to restore only entries no longer existing in the translation dictionary
    • *ALL, to restore entries independently from their existence in the translation dictionary.
Figure 25 - Restoring a section of a multiple save file
Contact