Revision as of 18:44, 2 March 2016

Localization

Please read the references given in the reference section below.

Use to quickly edit translations
Found in menu option Translation Import/Export
Don't select table - all translation tables are exported
Export / Import as a ZIP file
Only centrally maintained fields are exported for ad_field
Do synchronize terminology after import, to set the names of centrally maintained fields
java.util.zip.ZipException: error in opening zip file: when used linux ark to compress file, using command line worked fine.

Tick Multi Lingual Translations on the Client window (set the language as well.) Run synchronize doc translations, restart app server. Translation tab shows on document window in client.

Remember to enable multi lingual translations for your client (see above)
Create table ending with _Trl
NB _Trl must begin with capital T
Look at ad_element_Trl for an example of columns you need in your table
The key of the table must be ticked 'parent link'
Make sure that the SQL definition of the table has a primary key defined (Parent_ID And Language as columns)
- Otherwise, "No primary key found for table ..." error will be thrown.
Add a translation tab to your window, tab & field, with 'translation tab' ticked
Set the tab level to 1, or the applicable tab level
Set the parent link column
The column(s) to be translated (on the main table, not the _Trl table) must be ticked on the table & column as 'translated' (see under technical)
Login to System and open the Language window, find your language, and click on language maintenance. Select 'Add missing translations'
Remember: new translation records are not added using the translation window, but rather using 'Add missing translations', and also automatically, when a new main record is created.
- Client level translations are added at the same time

Lookup the client's language under the client window.
Find the language under System, in the Language window.
Note the ISO Country code
Find the country by ISO Country Code, under System, in Country, Region & City window

Use resource bundles to translate reports.

Refer: http://wiki.idempiere.org/en/Multi-Lingual_Jasper
Subreports need a parameter to be added. Refer: http://wiki.idempiere.org/en/Finding_resources_in_JasperReports
Set resource bundle property of report to same as report name
Set sub report resource bundle to blank
Subreport then uses same bundle as main report
if having problems seeing properties in deployed report, examine /tmp/reportname* (TEMP folder in windows), to see if correct files have been deployed

@@ Line 32: / Line 32: @@
 * The column(s) to be translated (on the main table, not the _Trl table) must be ticked on the table & column as 'translated' (see under technical)
 * Login to System and open the '''Language''' window, find your language, and click on '''language maintenance'''. Select 'Add missing translations'
-* Remember: new translation records are not added using the translation window, but rather using 'Add missing translations'.
+* Remember: new translation records are not added using the translation window, but rather using 'Add missing translations', and also automatically, when a new main record is created.
 ** Client level translations are added at the same time