4 Translating Resource Text

This chapter contains the following topics:

4.1 Understanding Resource Files

Resource files (for example, files with extensions such as .rc, .dll, .exe) are the applications that are generated by third-party tools (C++ and Java). They appear throughout JD Edwards products and include error messages, toolbar menus, and the legal disclaimer. Resource file items can be a single word or a short paragraph. To ensure consistency, one translator should translate all resource files for one language using the Resource Text Translation program (P79201) in Oracle's JD Edwards EnterpriseOne Translation Tools. Resource files occur throughout JD Edwards EnterpriseOne software; they are grouped by file rather than product code.

You translate all resource items using the F79201: Resource Text Translations (RTT) tool. In addition to translating items, you can retrieve and use existing translations, check the spelling of the text, change the status of an item, save translated items, search for and replace target text, and so on.

You have three options when translating resource files. You can enter a translation manually, copy the source text that has already been translated manually, or use suggestions.

Many items in the resource files include a hot key. Hot keys can be localized to a specific language, but standards should be followed for consistency.

Because resource files are not grouped by product code, you generally translate them in the order that they appear in the tool (RTT). Resource text, however, is grouped by the resource file and parent identifier.


Resource files have names such as jdeuser.dll, and the items are contained in these files. The parent identifier is sometimes just a number (for example, 128), and does not necessarily tell you what kind of item you are translating. Often, you can deduce that you are working with a dialog box, but nothing as specific as the Calendar or Calculator.

4.2 Translating Service Pack Resources

This section provides an overview of service pack resource translation and discusses how to translate service pack resources.

4.2.1 Understanding Service Pack Resource Translation

Resource Text Translation (RTT) comes from DLLs and Java files that are part of ClearCase and the service pack trees. This information is not part of standard pristine data sources or tables. The translating service pack resources process includes an extract and update for the resources in the DLLs and Java files.

The Resource Life Cycle is associated with service packs and not a major release.

4.2.2 Translating Service Pack Resources

You run several different processes when you translate service packs. the programs could be in a different location (Rtt.exe, for example). These steps provide high-level guidance so that you do not miss any of the steps in the process.

The mastering group should perform some of these steps, and the translation group should perform others. These steps indicate which group should perform which task.

To translate service pack resources:

  1. The mastering group extracts the RTT files into a source Delta environment using the Rtt.exe.

  2. The mastering group runs the Delta Process using the Translation Delta Process program (R79800) for each compare environment for each tier.

  3. The mastering group runs the Check Delete Status program (R79802) to update orphaned records in the status stable.

    The process runs all languages simultaneously for each compare environment.

  4. Either the translation group or the mastering group rebuilds the keys by language using either the Delta Purge and Rebuild Process program (R79801) or the Resource Text Translation program (P79201).


    Any translator can perform this step. Use the Rebuild Key option from the Form menu of the Resource Text Translation program (P79201).
  5. The translation group translates the source items using the Resource Text Translation program (P79201).

    Translate each language.

  6. The mastering group runs the Delta Purge and Rebuild Process program (R79801) to purge the records that are set to a status of 99 (Purge from System).

    Run this process once for each language.

  7. The mastering group builds the package (.dll and .jar files) using the Rtt.exe.

    Run this process once for each language.

  8. The translation group checks the package (.dll and .jar files) using Visual C++, JD Edwards EnterpriseOne Standalone, and language install on a web server for Java and HTML.

    Check the package for each language.


    Everything done by language needs to use the appropriate setup for the language and code pages.

4.3 Translating Resource Text

This section provides an overview of resource text translation and discusses how to translate resource text.

4.3.1 Understanding Resource Text Translation

Resource Text Translation (RTT) finds and displays items by matching the search criteria that you enter in the fields or on the Query by Example (QBE) line. The information that you enter in these fields remains until you change it. The files that appear contain the items that you will translate.

4.3.2 Translating Resource Text

To translate resource text:

  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 F7920: Resource Text Translations (RTT).

  2. On Work With Resource Text Translation, complete the Selected File Name, Status, and Language fields, and click Find.


    The F7920: Resource Text Translations (RTT) tool retrieves the resource items that match the search criteria and displays them in the detail area.

    Any language that you search on that is not specified in the user profile is read-only.

    If you leave any of the fields blank, the system uses the default value of * (asterisk), which equals a search for all items.

  3. On Work With Resource Text Translation, select a record in the detail area and then click Select.

  4. On Resource Text Translation, click the item in the menu tree that you want to review or translate.

  5. Enter the translation in the Target window, and then click OK to save it.

    You must enter a translation. The system does not save blank records.