THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.
...
Also refer to Tips for UI labels translation.
| Info |
|---|
Some POS labels are handled by XUI not OFBIz. You can use a plugin like RBE to edit those XuiLabels.properties |
Location of config files
located in the configuration subdirectories as follows:OFBIZ_HOME/applications/<appname>/config
...
Interested to understand how you make references to the i18n labels in code? Then read this: Text Translation.
Translation of OFBiz assets with built-in i18n options
...
Most typically, the entity.name, entity.description and entity.longdescription attributes can be internationalized. A table listing the i18n options of respective entity attributes will be worked in here soon.
| Note | ||
|---|---|---|
| ||
When using i18n on these entities, the "direct" attributes must be empty, otherwise the CMS lookup will not occur. |
...
| Info | ||
|---|---|---|
| ||
The content of HTML Meta tags on product pages are handled in
The following content will be handled as i18n content, i.e. locale/fallback locale applies in <HTML><HEAD>...<META type="keyword" ...> tags:
The following content will be handled as i18n content, i.e. locale/fallback locale applies in <HTML><HEAD>...<META type="description" ...> tags:
Using this will help you with localized SEO (=Search Engine Optimisation) projects. |
...
Translation of Text Elements using the CMS
...