Difference between revisions of "NF1.0 Base Language Flexible"

From iDempiere en
Line 22: Line 22:
 
Add AD_Language.DisplayName (this is how the language will be shown on login list)
 
Add AD_Language.DisplayName (this is how the language will be shown on login list)
 
For backward compatibility - set properly the values of the 37 hardcoded languages on Language.java
 
For backward compatibility - set properly the values of the 37 hardcoded languages on Language.java
 +
 +
 +
We have now a process in System called Change Base Language - you can use this process to swap en_US to another base language of your preference, or if you want a system without base language just set it to a non-login language.
 +
PO.updateTranslations and Synchronize Doc Translation were changed to synchronize any change on the master table (i.e. C_Charge) to the corresponding translation table (i.e. C_Charge_Trl) for the language selected by tenant.
 +
 +
[[File:lenguage1.png]]
 +
  
 
'''Technical Info:''' [http://jira.idempiere.com/browse/IDEMPIERE-136 IDEMPIERE-136] [http://jira.idempiere.com/browse/IDEMPIERE-489 IDEMPIERE-489]
 
'''Technical Info:''' [http://jira.idempiere.com/browse/IDEMPIERE-136 IDEMPIERE-136] [http://jira.idempiere.com/browse/IDEMPIERE-489 IDEMPIERE-489]

Revision as of 01:46, 5 July 2013

Feature: Base Language Flexible

Goal: Technical

Seed Contributor: Kenos

Sponsor: Trek Global

Description:

Please refer [1]

The main idea is to save/update/load all fields that are translated directly to/from the *_TRL tables, depending on the actual login language. AND to create _TRL entries for ALL system languages (so also for en_us) - so every language would be treated the same way. A nice benefit from this approach would be that we could throw away all views that have also a tranlated view - we just keep the translated views since every language is a translation then..


Actually iDempiere is using a hardcoded definition of languages from Language.java - to configure or change the behavior of a language is needed to modify that table. iDempiere has the table AD_Language where the user can configure some things about the language - but the system doesn't take into account any of those changes. This ticket is to let iDempiere use the language changes configured on AD_Language table. Suggested changes: Add AD_Language.AD_PrintPaper_ID column Add AD_Language.DisplayName (this is how the language will be shown on login list) For backward compatibility - set properly the values of the 37 hardcoded languages on Language.java


We have now a process in System called Change Base Language - you can use this process to swap en_US to another base language of your preference, or if you want a system without base language just set it to a non-login language. PO.updateTranslations and Synchronize Doc Translation were changed to synchronize any change on the master table (i.e. C_Charge) to the corresponding translation table (i.e. C_Charge_Trl) for the language selected by tenant.

Lenguage1.png


Technical Info: IDEMPIERE-136 IDEMPIERE-489

Cookies help us deliver our services. By using our services, you agree to our use of cookies.