Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0006019 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Tools] openbravo2po | critical | always | 2008-11-18 13:38 | 2011-03-31 11:13 | |||
| Reporter | gforcada | View Status | public | |||||
| Assigned To | pheenan | |||||||
| Priority | normal | Resolution | fixed | |||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | |||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Review Assigned To | ||||||||
| Summary | 0006019: Move the trl="Y" from <row> to <value> tag | |||||||
| Description | If you start translating xml files from Openbravo ERP and within a row that contains 3 values (name, help and description) you only translate name the Openbravo2po tool marks the whole row as translated even if help and description are not translated. This is more problematic if you then export them to po files with runXML2PO. You end with po files that claim to be fully translated but that aren't translated at all (or maybe just some strings but not all). | |||||||
| Proposed Solution | Move the trl switch from <row> tag to <value> tag and fix runXML2PO to ensure that only the really translated <value> are translated in the resulting po files. Note that maybe this change implies more changes somewhere (I really don't know). | |||||||
| Tags | commsup_sprint6 | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0013315) pheenan (reporter) 2009-02-10 16:32 |
When importing the file following a template merge the isTrl flag in the value is ignored. The problem is when exporting the language to XML this flag is not generated correctly. Therefore all lines are flagged with isTrl=N regardless of whether they have been translated or not. Introduce handling for the isTrl flag into the import and export process in Openbravo ERP. This can then be integrated with teh openbravo2po-valueTrl branch functionality. |
|
(0013322) pheenan (reporter) 2009-02-10 17:23 |
Update src.org.openbravo.erpCommon.ad_forms.Translation.java to include the isTrl flag in the value line of the exported xml file. |
|
(0013323) pheenan (reporter) 2009-02-10 17:25 |
Fixed in svn commit 13027. Updating export translation process to flag value lines as translated or not. Used in conjunction with openbravo2po to improve efficiency in updating localisations. src/org/openbravo/erpCommon/ad_forms/Translation.java |
|
(0013398) gforcada (reporter) 2009-02-12 11:22 |
Great news! Thanks a lot :) |
|
(0013399) gforcada (reporter) 2009-02-12 11:24 |
Wiki should be updated though |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-11-18 13:38 | gforcada | New Issue | |
| 2008-12-09 14:55 | pheenan | Assigned To | => pheenan |
| 2009-02-10 16:32 | pheenan | Note Added: 0013315 | |
| 2009-02-10 17:23 | pheenan | Status | new => scheduled |
| 2009-02-10 17:23 | pheenan | Note Added: 0013322 | |
| 2009-02-10 17:23 | pheenan | fix_in_branch | => trunk |
| 2009-02-10 17:25 | pheenan | Status | scheduled => resolved |
| 2009-02-10 17:25 | pheenan | Resolution | open => fixed |
| 2009-02-10 17:25 | pheenan | Note Added: 0013323 | |
| 2009-02-12 11:22 | gforcada | Note Added: 0013398 | |
| 2009-02-12 11:24 | gforcada | Note Added: 0013399 | |
| 2009-02-20 09:30 | PavelPonomarev | Tag Attached: commsup_sprint6 | |
| 2011-03-31 11:13 | dalsasua | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |