W.I.P.

Guide to OFBiz-i18n, Internationalisation of OFBiz

Looking around the WIKI there are few hints (and even less concrete guides) towards what needs to be done in order to add more locales to an OFBiz setup.

...

• Re-configuration of General Ledger 
• Tax configuration
• Extension of GeoData
  
  
  

Translation of Application labels

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.

Location of config files

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

OFBIZ_HOME/framework/<appname>/config

OFBIZ_HOME/specialpurpose/<appname>/config

The naming convention is <appname>UiLabels.xml.

Most likely there will also be <appname>HelpUiLabels.xml, <appname>EntityLabels.xml and possibly other files there. Just check through an see what merits your translation.

Activation

 The activation of changed configuration files is easy: Restart the OFBiz application. These configuration files are read in every time the OFBiz application container starts. Hence: Edit > Save > Restart > Use is the activation sequence.

Translation of OFBiz assets with built-in i18n options

Some OFBiz entities have built-in i18n options (Catalog, Product). 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: 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)

Translation of Text Elements using the CMS

MORE TO COME SOON (worked example)

(to be continued)