Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0007085
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] E. Translationminoralways2009-01-23 10:182022-02-01 08:08
ReportergforcadaView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision8226c24bc331
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0007085: Don't export columns that doesn't contain text

DescriptionWhen a language is exported and a row doesn't contain a Description, but others has, an empty <value column="Description" original=""></value> is added to that <row>, for example:

<row id="100" trl="Y">
  <value column="Name" original="Table">Table</value>
  <value column="CommitWarning" original=""></value>
  <value column="Description" original="Define tables that Openbravo can access in the database.">Define tables that Openbravo can access in the database.</value>
  <value column="Help" original="Define tables that Openbravo can access in the database.">Define tables that Openbravo can access in the database.</value>
</row>

The CommitWarning column is empty in this row, so it shouldn't be exported at all.

And when importing the translation, if a row doesn't have a column it should skip that column for that row (or add the default language - English - translation, if any).

This is somewhat related to https://issues.openbravo.com/view.php?id=7009 [^]
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0012932)
rafaroda (developer)
2009-01-30 17:15

 Hi Gil,

First of all, could you please write down the steps to reproduce this issue.

Secondly, is this really a defect in the 'Export translation' functionality or a feature request?

Thank you.
(0012988)
gforcada (reporter)
2009-02-02 10:30

 Sorry it's a feature request.

The issue is that when those xml files with empty <value> are exported to po files with Openbravo2PO they add false translations which is not an issue for a translator, but is an issue for a statistics system.

If we remove those <value> when exporting to xml files Openbravo2PO or any other tool used to interact with the xml files will not have empty strings to translate.
(0013288)
rafaroda (developer)
2009-02-10 10:12

 Reminder sent to: gforcada

Gil, can you please add the steps to reproduce this issue?

Thank you.
(0013394)
gforcada (reporter)
2009-02-12 10:38

 Steps:

- Export a language from Openbravo ERP to xml files
- run "grep 'original=""' *.xml" in the directory that contains the language xml files
- you will see 16834 lines in the it_IT/trunk for example (it was updated on 2009-02-11)

All those <value> are meaningless since they doesn't contain anything. and when exported to po files they cause confusions when calculating the statistics.
(0013785)
pjuvara (reporter)
2009-02-20 09:09

 Feedback has been provided.
(0037157)
hgbot (developer)
2011-05-18 16:13

 Repository: erp/mods/org.openbravo.localization.spain.referencedata.taxes
Changeset: 8226c24bc331167c0e9a1d190a97e414807f06c1
Author: Javier Etxarri <javier.echarri <at> openbravo.com>
Date: Wed May 18 13:31:04 2011 +0200
URL: http://code.openbravo.com/erp/mods/org.openbravo.localization.spain.referencedata.taxes/rev/8226c24bc331167c0e9a1d190a97e414807f06c1 [^]

Fixes issue 7085: Dataset should not contain any tax checked as default

---
M referencedata/standard/Impuestos_ES.xml
---
(0038226)
shuehner (administrator)
2011-06-10 12:40

 Reopen, as commit resolving it has intended for another issues (17085)

- Issue History
Date Modified Username Field Change
2009-01-23 10:18 gforcada New Issue
2009-01-23 10:18 gforcada Assigned To => rafaroda
2009-01-23 10:18 gforcada sf_bug_id 0 => 2530698
2009-01-23 16:37 jordimas Issue Monitored: jordimas
2009-01-28 08:48 rafaroda version => trunk
2009-01-30 17:15 rafaroda Note Added: 0012932
2009-01-30 17:15 rafaroda Status new => feedback
2009-02-02 10:30 gforcada Note Added: 0012988
2009-02-10 10:11 rafaroda Assigned To rafaroda => pheenan
2009-02-10 10:12 rafaroda Note Added: 0013288
2009-02-12 10:38 gforcada Note Added: 0013394
2009-02-20 09:09 pjuvara Note Added: 0013785
2009-02-20 09:09 pjuvara Status feedback => new
2009-03-03 12:33 rafaroda Status new => acknowledged
2009-03-03 12:33 rafaroda Type defect => feature request
2009-03-24 10:43 AinhoaPagola Assigned To pheenan => alostale
2011-05-18 16:13 hgbot Checkin
2011-05-18 16:13 hgbot Note Added: 0037157
2011-05-18 16:13 hgbot Status acknowledged => resolved
2011-05-18 16:13 hgbot Resolution open => fixed
2011-05-18 16:13 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/mods/org.openbravo.localization.spain.referencedata.taxes/rev/8226c24bc331167c0e9a1d190a97e414807f06c1 [^]
2011-06-10 12:40 shuehner Note Added: 0038226
2011-06-10 12:40 shuehner Status resolved => new
2011-06-10 12:40 shuehner Resolution fixed => open
2017-04-10 14:38 alostale Assigned To alostale => platform
2022-02-01 08:08 alostale Assigned To platform => Triage Platform Base

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker