Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0008843 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] E. Translation | major | always | 2009-04-29 19:31 | 2010-04-30 00:00 | |||
| Reporter | gforcada | View Status | public | |||||
| Assigned To | alostale | |||||||
| Priority | urgent | Resolution | out of date | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | pi | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0008843: Please stick with the AD_FORM_TRL_en_US.xml filename | |||||||
| Description | 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. | |||||||
| Proposed Solution | 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. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0015952) rmorley (reporter) 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 (reporter) 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 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-04-29 19:31 | gforcada | New Issue | |
| 2009-04-29 19:31 | gforcada | Assigned To | => rafaroda |
| 2009-04-29 19:31 | gforcada | Regression testing | => No |
| 2009-04-30 10:33 | rafaroda | Assigned To | rafaroda => alostale |
| 2009-04-30 10:33 | rafaroda | Priority | normal => high |
| 2009-04-30 10:33 | rafaroda | Status | new => scheduled |
| 2009-04-30 10:33 | rafaroda | version | => pi |
| 2009-04-30 11:56 | rmorley | Note Added: 0015952 | |
| 2009-04-30 18:32 | gforcada | Note Added: 0015975 | |
| 2010-01-05 13:40 | iciordia | Priority | high => urgent |
| 2010-04-29 17:00 | alostale | Status | scheduled => closed |
| 2010-04-29 17:00 | alostale | Resolution | open => out of date |
| 2010-04-30 00:00 | anonymous | sf_bug_id | 0 => 2994420 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |