Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012944Openbravo ERP01. General setuppublic2010-04-12 20:252010-05-06 00:00
Reportervmromanos 
Assigned Toalostale 
PriorityimmediateSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS20OS VersionDebian 5.0
Product Version2.40MP12 
Target Version2.40MP13Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012944: trl attribute in language XML files is always set to "Y"
DescriptionThe XML structure of the language files is:

<row id="101" trl="Y">
    <value column="MsgText" original="zero">cero</value>
    <value column="MsgTip" original=""/>
</row>

Where the trl attribute indicates whether the string is translated or not.

In previous versions of Openbravo 2.40, this attribute was properly set to the right value, however right now it's always set as "Y".

This bug does not allow the translator to properly identify which strings are remaining to be translated and it makes almost impossible to manage translations from a localizer point of view.

Note: I have just checked it in Openbravo 2.40
Steps To Reproduce1- First of all you will need to apply the patch available in 0010914 to fix an issue that is blocking this one
2- Import the Spanish language (available at https://dev.openbravo.com/websvn/localization/translations/es_ES/branches/2.40/ [^]) using the normal procedure described at http://wiki.openbravo.com/wiki/Translating_Openbravo [^]
3- Export the language.
4- Run a diff in each of the XML files between the old version and the exported one and you will see that there are lots of trl changed to "Y". Example for the AD_MESSAGE table:
< <row id="1000200002" trl="Y">
---
> <row id="1000200002" trl="N">
21919c21919
< <row id="1000200003" trl="Y">
---
> <row id="1000200003" trl="N">
5- If you open the new version of the file, and you find one of these rows, you will realize that they're not translated into Spanish and they have the trl="Y". Example:
  <row id="1000200002" trl="Y">
    <value column="MsgText" original="Order line">Order line</value>
    <value column="MsgTip" original=""/>
  </row>
Proposed SolutionThe trl attribute must work as before
Additional Information
TagsNo tags attached.
Relationships
depends on defect 00109142.40MP13 closed alostale Export translation does not work 
depends on backport 00132132.40MP13 closed alostale trl attribute in language XML files is always set to "Y" 
blocks defect 0012925 closed vmromanos Report trial balance (PDF) is not translated at all 
blocks backport 0013123 closed vmromanos Report trial balance (PDF) is not translated at all 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-04-12 20:25vmromanosNew Issue
2010-04-12 20:25vmromanosAssigned To => adrianromero
2010-04-12 20:25vmromanosRelationship addeddepends on 0010914
2010-04-12 20:26vmromanosRelationship addedblocks 0012925
2010-04-26 16:37dalsasuaRelationship addedblocks 0013123
2010-04-28 10:20dmitry_mezentsevNote Added: 0026747
2010-05-04 13:33adrianromeroStatusnew => scheduled
2010-05-04 13:33adrianromerofix_in_branch => pi
2010-05-04 13:35adrianromeroTarget Version => 2.40MP13
2010-05-04 13:35adrianromerofix_in_branchpi =>
2010-05-04 13:37adrianromeroIssue cloned0013213
2010-05-04 13:37adrianromeroRelationship addeddepends on 0013213
2010-05-04 16:57adrianromeroNote Added: 0026926
2010-05-04 16:57adrianromeroAssigned Toadrianromero => alostale
2010-05-04 16:57adrianromeroPrioritynormal => immediate
2010-05-05 08:57alostaleNote Added: 0026951
2010-05-05 08:57alostaleStatusscheduled => closed
2010-05-05 08:57alostaleResolutionopen => no change required
2010-05-06 00:00anonymoussf_bug_id0 => 2997334

Notes
(0026747)
dmitry_mezentsev   
2010-04-28 10:20   
Changed this issue to OBN course it is blocking OBN fix - 0012925.
(0026926)
adrianromero   
2010-05-04 16:57   
Set to inmediate because it blocks an obnetwork issue near to expire
(0026951)
alostale   
2010-05-05 08:57   
This is not a 2.50 issue, fixed backport in 2.40