Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0008843Openbravo ERPE. Translationpublic2009-04-29 19:312010-04-30 00:00
gforcada 
alostale 
urgentmajoralways
closedout of date 
5
pi 
 
Core
No
0008843: Please stick with the AD_FORM_TRL_en_US.xml filename
In Openbravo ERP 2.40 whenever you exported a translation it produces a number of xml files with the filename like:

TableName + _TRL_ + ll + CC + .xml

Where TableName was the given table, ll was the language code (two letters) and CC was the Country (two letters also).

Right now, exporting the translations from a 2.50 virtual appliance (the Virtualbox one) it gives me this filename:

TableName + ll + CC + .xml

Note that the _TRL_ has been erased.
I think that there's any benefit to erase the _TRL_ from the filenames since ALL 45 translations efforts that has been already started have the _TRL_ in their translation files.

The big concern here is that with the http://translations.openbravo.com [^] and the effort that have to be done to automate the process of updating the source language that's used as a base (the en_US translation) if we keep changing the filename format there's no way to really automate it because the maintainer will have to have always an eye to it.
No tags attached.
Issue History
2009-04-29 19:31gforcadaNew Issue
2009-04-29 19:31gforcadaAssigned To => rafaroda
2009-04-29 19:31gforcadaRegression testing => No
2009-04-30 10:33rafarodaAssigned Torafaroda => alostale
2009-04-30 10:33rafarodaPrioritynormal => high
2009-04-30 10:33rafarodaStatusnew => scheduled
2009-04-30 10:33rafarodaversion => pi
2009-04-30 11:56rmorleyNote Added: 0015952
2009-04-30 18:32gforcadaNote Added: 0015975
2010-01-05 13:40iciordiaPriorityhigh => urgent
2010-04-29 17:00alostaleStatusscheduled => closed
2010-04-29 17:00alostaleResolutionopen => out of date
2010-04-30 00:00anonymoussf_bug_id0 => 2994420

Notes
(0015952)
rmorley   
2009-04-30 11:56   
Let's agree to stick with AD_FIELD_TRL_en_US.xml naming convention (unless someone can come up with a compelling reason for it to be different).
(0015975)
gforcada   
2009-04-30 18:32   
Note that right now there are some translation files that have the TRL while other doesn't have it.

The files that have already the TRL are:
C_COUNTRY
C_CURRENCY
C_DOCTYPE
C_UOM

The other 17 files doesn't contain it.

I recall this because some weeks ago I filled [1] because exactly those 4 files had 2 TRL in their names.

Seems we haven't found a proper solution until now.

[1] https://issues.openbravo.com/view.php?id=8368 [^]