Page History

...

The labels for the OFBiz GUI applications are the most evident part to change for an i18n project. They are part of the release and serve the purpose of 'resource packs' known from claqssic Java development.

Also refer to Tips for UI labels translation.

Location of config files

located in the configuration subdirectories as follows:OFBIZ_HOME/applications/<appname>/config

...

Panel
This section assumes you have understood the relationship of Content, ContentAssociations and DataResources. Also, you should understand how a DataResource can be provided to the system.

Some OFBiz entities have built-in i18n options (Catalog, Product). Check out how to translate Products or Categories Name and Descriptions, have a look at How to localize Product and Categories descriptions.
You can find out which entities provide this option when searching for "*Content" in the entitydef configuration files (which will then list out all occurences of a <entityname>Content entity.
Most typically, the entity.name, entity.description and entity.longdescription attributes cna be internationalized. Note that by default, the entity.description entries are also used as in HTML HEAD META type="keyword" tags, so using this can help you with localized Search Engine Optimisation projects.
NOTE: When using i18n on these entities, the "direct" attributes must be empty, otherwise the CMS lookup will not occur.

MORE TO COME SOON (worked example)

...

Some language communities have started common dictionaries in order to align translation options and agree on some special terms. Examples are:

• Wiki Markup
  \[Danish Dictionary\]

• Wiki Markup
  \[German Dictionary\]

MORE TO COME SOON (worked example)

...

• Dictionary for Danish translations
• Dictionary for Dutch translations
• Dictionary for translations to German
  RELATED OFBIZ Wiki Material (unscreened yet):
• Text Translation
• Internationalization