Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0042076 | Openbravo ERP | Z. Others | public | 2019-10-21 19:31 | 2022-02-01 07:24 |
Reporter | AtulOpenbravo | ||||
Assigned To | Triage Platform Base | ||||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0042076: Openbravo2PO Tool should generate XML in the same way Openbravo exports when using Translation Import/Export | ||||
Description | Openbravo2PO Tool should generate XML in the same way Openbravo exports when using Translation Import/Export. It is found that XML files generated by Openbravo2PO Tool from PO files there is difference in the XML files as below: At the beginning of XML file generated using Openbravo2PO Tool from PO files, A. baseLanguage property is missing in the compiereTrl tag. <?xml version="1.0" encoding="UTF-8" standalone="no"?> -<compiereTrl language="fr_FR" table="OBUISEL_SELECTOR" version=""> +<compiereTrl baseLanguage="en_US" language="fr_FR" table="OBUISEL_SELECTOR" version=""> B. Each value in the each row, isTrl property is missing <row id="FF808181312DA8D801312DDE869B000C" trl="Y"> - <value column="Name" original="Product selector">Article</value> - <value column="Description" original=""/> - <value column="Help" original=""/> + <value column="Name" isTrl="Y" original="Product selector">Article</value> + <value column="Description" isTrl="N" original=""/> + <value column="Help" isTrl="N" original=""/> | ||||
Steps To Reproduce | Step A - Login as System Administration. - Navigate to Languages window. - Select language with code es_ES and run Verify Language process. - Navigate to Import/Export Translation window. - Select Language Spanish (Spain) and execute Export button process. Following document http://wiki.openbravo.com/wiki/Projects:Translation_PO_Merge/User_Documentation [^] Step B - For translation of any module for eg: org.openbravo.advpaymentmngt - Using Openbravo2PO tool, translate XML files to PO files. - Edit PO Files and update translation for few records - Using Openbravo2PO tool, translate PO files to XML files. - Now check XML files generated in Step A and Step B, for any XML file, it will have difference as mentioned in the description above. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2019-10-21 19:31 | AtulOpenbravo | New Issue | |||
2019-10-21 19:31 | AtulOpenbravo | Assigned To | => Triage Finance | ||
2019-10-21 19:31 | AtulOpenbravo | Modules | => Core | ||
2019-10-21 19:31 | AtulOpenbravo | Triggers an Emergency Pack | => No | ||
2019-10-21 19:31 | AtulOpenbravo | Assigned To | Triage Finance => platform | ||
2022-02-01 07:24 | alostale | Assigned To | platform => Triage Platform Base |
There are no notes attached to this issue. |