The following list shows the main tasks to perform when you localize extensions to the grammar editor:
Examine the XML files for the grammar templates that ship in the Oracle Commerce Platform product distribution (the source .xml files are in the distribution along with the .ser files), and consider their relationship to the behavior of the user interface.
Prepare locale-specific files that correspond to the template names described earlier in this document, using the language and optional country name to form the filename according to the search rules.
Select a suitable character encoding and declare it in the grammar.
Translate all description and editor-text elements using the above encoding to represent the translation.
Reorder the children of sequence elements where feasible—in general, this is only permitted where the children are either noise words (value-less tokens) or constructs labeled with unique IDs.
Eventually, after development and testing, serialize the XML files into correspondingly named .ser files.