5 Translating the Data Dictionary

This chapter contains the following topics:

5.1 Understanding Data Dictionary Translation

This section discusses:

  • Data dictionary items.

  • The data dictionary translation process.

  • Data dictionary items and the Form Design Aid (FDA) translation tool.

  • The SAME shortcut.

  • Data dictionary translation tools.

  • Data dictionary item navigation.

  • Data dictionary space constraints.

5.1.1 Data Dictionary Items

Data dictionary items include check boxes, radio buttons, text fields, grid items, and help text that appear throughout Oracle's JD Edwards EnterpriseOne software. The data dictionary stores the descriptions for these items. Each data dictionary item contains at least one of the these components:

  • Alias: an alpha code given to a data dictionary item.

  • Alpha description: the title that appears in the help text in the software when you press F1.

  • Row description: the text that describes form controls.

  • Column description: the text that describes grid columns.

  • Glossary: the full description text in paragraph form when you press F1.

5.1.2 The Data Dictionary Translation Process

Translating a data dictionary item is an iterative six-step process, as described here:

  1. Select the data dictionary item that you want to translate.

  2. Review both the data item components for context and the suggestions for appropriateness.

  3. Enter the translation manually or copy existing translations.

  4. Check the spelling.

  5. Review space constraints.

  6. Save the translation and start the process over again.

JD Edwards data dictionary translation tools use many of the same processes repeatedly.

5.1.3 Data Dictionary Items and the FDA Translation Tool

The data dictionary translations that you enter are the translations for their corresponding forms. Therefore, when you access a form in the FDA Translation Tool (P797501), the data dictionary translation appears as the field description unless the item has an override. The status for the form items in the FDA Translation Tool remains at a status of 20 (Untranslated) until you save the translation. When you save the translation, the item moves to a status of 15 (FDA/RDA DD Default).

When you edit a data dictionary translation, FDA items that are not overridden by a language are set to a status of 25 (Edit (Review)). You can view the list of language-overridden and non-overridden forms in the English Non-Overridden Forms box. When you access the affected forms in the Form Design Aid (FDA) Translation Tool, the edited translation appears in the Translation field.

5.1.4 The *SAME Shortcut

When you are translating an alpha description that has jargon applied, two fields appear for both the Source and Target columns: Alpha - Base and Alpha Description. If the translation of the base description is correct for the alpha description, you can reuse the base description by entering *SAME in the Translation field.

5.1.5 Data Dictionary Translation Tools

You use three data dictionary language translation tools to translate data dictionary items:

  • F00165 (GT92002): Data Dictionary (DD) Glossaries.

  • F9202: Data Dictionary (DD) Row / Column.

  • F9203: Data Dictionary (DD) Alpha.

You access all of these tools through the Translation Applications menu (GH791).

5.1.6 Data Dictionary Item Navigation

When you access any of the data dictionary translation tools, the data items for the system and status that you specified appear. You can select an item by double-clicking it or by choosing the item in the detail area and clicking Select.

If you are looking for a specific item, you can use the Find button to search by alias. You also can search for a specific item from a different system. To display all items in another system, specify a new system in the Product Code field. You can view and edit translation items in a product code that is not specified in the user profile.

The Find/Browse (Work With...) form enables you to search for data dictionary items that require translation or review. You can search for data items by product code, language, status, or all three. When you select an item on one of these forms, you access the Data Dictionary Translations form.

5.1.7 Data Dictionary Space Constraints

A fixed amount of space is available for most data dictionary items. Alpha and row descriptions are allotted 40 characters, and column descriptions are allotted 20 characters for the top translation field and 20 characters for the bottom translation field.

Although the translation might fit within the space allotted in the data dictionary translation tool, it might not fit in the space allotted in the Form Design Aid (FDA) Translation Tool. In other words, not all forms allow 40 characters for controls.

A data dictionary item can be used on many forms, and those forms might allow different amounts of space. The data dictionary translation tool finds the form that allows the least amount of space, and displays the amount so that you can enter a translation that will fit in all forms. If you exceed the space available, a warning message appears.

Note:

To view a non-overridden form or a form with a translation override, click the form name in the English Non-Overridden Forms box.

5.2 Translating Alpha, Row, and Column Descriptions

This section provides an overview of alpha, row, and column descriptions and discusses how to edit data dictionary alpha, row, and column entries.

5.2.1 Understanding Alpha, Row, and Column Descriptions

The Data Dictionary Language Translation program (P799201) treats alpha descriptions as individual items with their own status codes. When you translate, you must select to work with either alpha, or row and column descriptions. Because most alpha descriptions have related row and column descriptions, you should translate alpha descriptions first.

Row and column descriptions make up one item. One status code applies to both descriptions.

5.2.2 Editing Data Dictionary Alpha, Row, and Column Entries

You can edit Alpha and Row, and Column Entries dynamically. Editing them dynamically enables you greater consistency when translating the data dictionary.

To edit data dictionary alpha or row, and column entries:

  1. From the Translation Applications menu (GH791), select either Senior Translations or Junior Translations, depending on whether you are a senior or junior translator, and then select either F9202: Data Dictionary (DD) Row / Column or F9203: Data Dictionary (DD) Alpha.

  2. On the Fix/Inspect (Work With...) form, locate the records that you want to translate.

  3. Select an item in the detail area and then click Select.

  4. On Data Dictionary Translation, select the Translation tab.

  5. Complete these target fields as necessary:

    • Alpha Description

      Enter an alpha description translation.

    • Row Description

      Enter a row description translation.

    • Column Title

      Enter a column title translation for Column 1 or Column 2 or both.

  6. Click OK.

    Note:

    JD Edwards Translation Tools accept a blank translation field only for Column Title 2 fields. If you are unsure about a translation, change the status of the item to 25 (Edit/Review) and review it later.

5.3 Translating Glossary Entries

This section provides an overview of glossary translation and discusses how to:

  • Translate glossary entries.

  • Filter glossaries.

  • Export glossaries.

  • Translate glossaries in a translation memory tool.

  • Import glossaries.

  • Validate glossaries.

5.3.1 Understanding Glossary Translation

The glossary is the help text that you see when you press F1. As you translate items, review the glossary entry to understand the context in which the data dictionary item is used. If you notice a mistake in the translated glossary entry, you can edit it on the Glossary tab.

Note:

JD Edwards Translation Tools do not have a translation memory.

5.3.1.1 File Naming Conventions for Exported Glossaries

On export, an XML file is saved to the file path specified in the File Path (Folder) field. The file name is created using the primary filters that are located on the Filter tab. The system uses these primary filters to build the export file naming convention. The File Path (Folder) field is limited to 30 characters.

Language_ TranslationStatus_SystemCode_GlossaryGroup_ DataItemFrom_DataItemTo .XML

This example illustrates a typical file name:

S_20_01_D_A_L.XML

S = Spanish

_20 = Untranslated

_01 = Address Book

_D = Glossary Group

_A = Data Items from A

_L = Data Items to L

Data items can be used in a range, such as A to L, or be specific, such as AN8 or LNGP.

In the file name on the XML tab, the wildcards (*) that you might have used on the Filter tab are substituted for a plus sign (+). A plus sign should work across all ASCII code pages. Additionally, the system uses a default path naming convention in the file name field. You should not change this naming convention.

5.3.2 Translating Glossary Entries

To translate glossary entries:

  1. From the Translation Applications menu (GH791), select either Senior Translations or Junior Translations, depending on whether you are a senior or junior translator, and then F00165 (GT92002): Data Dictionary (DD) Glossaries.

  2. On the Work With Glossary Data Dictionary Translation form, complete these fields and click Find.

    • Product Code

    • Glossary

    • Status

    • Skip from

    • Skip to

    • Language

  3. Select a data item in the detail area and then click Select.

  4. On Data Dictionary Translation, select the Glossary tab.

  5. Enter the translation in the lower media object window.

  6. Click OK to save the changes.

    The data item moves to the next workflow status. When you click OK, JD Edwards Translation Tools saves the changes and updates the status. The new glossary item will appear on the Translation tab the next time the Delta Process is run.

5.3.3 Filtering Glossaries

You can filter the glossaries to select exactly the ones that you want to export. You might want to filter glossaries to control the size of the output file.

To filter glossaries:

  1. From the Translation Applications menu (GH791), select either Senior Translations or Junior Translations, depending on whether you are a senior or junior translator, and then F00165: (GT92002) Data Dictionary (DD) Glossaries.

  2. On the Work With Glossary Data Dictionary Translation form, select the Filter tab, complete these fields, and then click Find:

    • Product Code

    • Glossary Group

    • Status

    • Skip From

    • Skip To

    • Language

      The user overrides save the values that you enter. These values reappear the next time that you log in.

      If you are using TRADOS, you should limit the size of the export to 0.5 MB. TRADOS can receive only files smaller than 0.5 MB in size. If the file is larger than 0.5 MB, TRADOS displays an error. You will have to experiment to determine how many records equal 0.5 MB because glossary records vary in size.

  3. Select the XML tab.

    You now can export glossaries from JD Edwards EnterpriseOne software.

5.3.4 Exporting Glossaries

After you complete the steps to filter glossaries, you must export the glossary data from JD Edwards EnterpriseOne software.

To export glossaries:

  1. On the Work With Glossary Data Dictionary Translation form, select the XML tab.

  2. Ensure that a file path is specified as a root directory in the File Path (Folder) field.

    A literal folder must be set up to handle the export or import (C:\ is the default folder). You must have the same file path set up in the root directory as is specified here. The File Path (Folder) field is limited to 30 characters.

  3. Ensure that you have a file name in the File Name field.

  4. Select one of these options:

    • Source

      Source text is exported.

    • Target

      Target text is exported.

    • Remove Hard Return

      Important:

      Selecting the Remove Hard Return option will remove all hard returns from the glossary records. The import process does not reinsert the hard returns.
  5. After you have entered the appropriate filters, specified the File Path (Folder) field, and determined the text option, from the Form menu, select Export.

    An XML file has been created.

  6. You can now use the translation memory tool to translate glossaries.

5.3.5 Translating Glossaries in a Translation Memory Tool

JD Edwards Translation Tools enable you to filter glossary information, including the alpha description, and create an XML file.

An example of a translation memory tool is TRADOS. The TRADOS Tag Editor enables you to use translation memory, including the TRADOS Translators Workbench. After translation is complete, the Translation Memory Editor saves translated data in an XML file. JD Edwards Translation Tools then import the XML file into the correct environment and code page in JD Edwards EnterpriseOne software and include preview functionality, which enables translators to validate the data.

To translate glossaries in TRADOS:

  1. Complete the steps to export glossaries:

  2. From the Form menu, select TM Editor.

  3. Either the TagEditor for TRADOS will open or the TM Editor listed in the processing options will open.

  4. Edit the glossaries using the translation memory functions.

  5. Select File Save as Target and replace the XML file.

    You now can import glossaries into JD Edwards EnterpriseOne software.

5.3.6 Importing Glossaries

You import the glossaries into JD Edwards EnterpriseOne software similar to the way that you exported them. You do this after you complete the steps to translate glossaries.

To import glossaries:

  1. Ensure that you have saved the data in the XML file.

    JD Edwards EnterpriseOne software uses the primary filters to build the import file naming convention. Ensure that the file name is exactly the same as when you exported it.

  2. From the Form menu, select Import.

  3. The status records are updated to Translation Memory at status 35 (Translation Memory).

    You now can validate the glossaries.

5.3.7 Validating Glossaries

You can validate the glossaries after you import them back into JD Edwards EnterpriseOne software. You do this after you complete the steps to import glossaries.

To validate glossaries in JD Edwards EnterpriseOne software:

  1. On the Work With Glossary Data Dictionary Translation form, select a record in the detail area, and then click Select.

  2. On the Data Dictionary Translation form, select the Glossary tab, and then verify that the glossary text was imported correctly.

  3. From the Form menu, select Target Preview, and then verify the format of the F1 help.

  4. Validate all glossaries that you imported again.

5.4 Copying Existing Items

To copy existing items:

  1. From the Translation Applications menu (GH791), select either Senior Translations or Junior Translations, depending on whether you are a senior or junior translator, and then select either F9202: Data Dictionary (DD) Row / Column or F9203: Data Dictionary (DD) Alpha.

  2. On the Fix/Inspect (Work With...) form, locate the records that you want to translate.

  3. Select an item in the detail area, and then click Select.

  4. On the Data Dictionary Translation form, select the Translation tab.

  5. On the Form menu, select one of these options:

    • Copy Source

      Copies the information from the source field to the target field.

    • Copy Alpha

      Copies the information for the alpha description into the row and column target field.

    • Copy Row

      Copies the information for the row description into the target field for the column description.

    • Copy Previous

      Copies the information from the last saved translation into the target field.

  6. Click OK to save the changes.