Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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, namely the current release or SVN trunk.

Most generally, there are three areas of concern when starting a translation of OFBiz into a different locale, i.e. a language and possibly a specific sub-locale:

...

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

Note that this document focusses on the CONFIGURATION of OFBiz Entities in order to display Text in a different Locale and possibly pay attention to different Legislation & Taxing in other Locales. This document does NOT aim to talk about technical localisation (Tech Folks, make sure you start at Adrian's Internationalization) or adding more local payment or shipping gateways, as t his is considered regular customisation.

A final section covers tools that can be used for the translations tasks and documents present in this wiki which refer to translations.

...




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)

Translation of Text Elements using the CMS

...