Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011051Openbravo ERPE. Translationpublic2009-10-20 15:342010-03-10 18:28
Reporternetworkb 
Assigned Toeduardo_Argal 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS30OS Version
Product Version2.50MP6 
Target Version2.50MP9Fixed 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
Summary0011051: Some lists are not correctly translated using spanish localization pack
DescriptionSome lists are not correctly translated using spanish localization pack
Steps To Reproduce-Install the spanish localization pack
-Go to Purchase Order or Sales order window
-See that the elements on the document types are not correctly translated to spanish
Proposed SolutionIn order to satisfy the customer needs until 0011247 is resolved please provide (attach to the issue):
1) The dataset
2) The postscript
Additional Information
TagsNo tags attached.
Relationships
related to defect 0007204 new jonalegriaesarte Localization Pack: Spain DocType translation to spanish 
related to feature request 0010506 scheduled Triage Platform Base Openbravo ERP It is allowed to change the name of a "Summary Tax Rate" but the name is not updated 
related to feature request 0010876 new iciordia Openbravo ERP Support for Business Objects Translations 
depends on feature request 0011247 closed iciordia Openbravo ERP Add capability to modules to execute postScripts 
has duplicate defect 00117982.40MP14 closed eduardo_Argal Openbravo ERP c_doctype elements are not translated after installing Spanish(Spain) translation in the application 
has duplicate defect 00120202.40MP15 closed eduardo_Argal Openbravo ERP Some Document Types are still missing in the translation script. 
related to feature request 0012348 new eduardo_Argal Openbravo ERP Some lists are not correctly translated using spanish localization pack 
Attached Filestxt C_DOCTYPE_TRL_es_ES_SCRIPT_ORA.txt (5,554) 2009-11-27 17:02
https://issues.openbravo.com/file_download.php?file_id=1995&type=bug
Issue History
Date ModifiedUsernameFieldChange
2009-10-20 15:34networkbNew Issue
2009-10-20 15:34networkbAssigned To => rafaroda
2009-10-20 15:59shuehnerNote Added: 0021213
2009-10-20 15:59shuehnerStatusnew => feedback
2009-10-20 16:13networkbNote Added: 0021216
2009-10-20 16:19networkbStatusfeedback => new
2009-10-20 18:27shuehnerRelationship addedrelated to 0007204
2009-10-21 07:55rafarodaNote Added: 0021237
2009-10-21 07:55rafarodaAssigned Torafaroda => vmromanos
2009-10-21 10:46vmromanosNote Added: 0021251
2009-10-21 10:47vmromanosNote Edited: 0021251
2009-10-21 12:33rafarodaNote Added: 0021265
2009-10-21 12:33rafarodaAssigned Tovmromanos => alostale
2009-10-21 12:33rafarodaPriorityimmediate => urgent
2009-10-21 12:33rafarodaStatusnew => acknowledged
2009-11-02 10:41networkbTarget Version => 2.50MP9
2009-11-09 13:57pnudingPriorityurgent => immediate
2009-11-09 14:52alostaleRelationship addedrelated to 0010506
2009-11-09 14:53alostaleRelationship addedrelated to 0010876
2009-11-10 10:35alostaleRelationship addeddepends on 0011247
2009-11-10 10:48alostaleAssigned Toalostale => eduardo_Argal
2009-11-11 10:17networkbNote Added: 0021711
2009-11-16 15:43dmitry_mezentsevNote Added: 0021863
2009-11-18 09:15rafarodaNote Added: 0021944
2009-11-18 09:19rafarodaNote Added: 0021946
2009-11-18 09:19rafarodaPriorityimmediate => urgent
2009-11-18 09:24alostaleNote Added: 0021948
2009-11-23 10:49dmitry_mezentsevNote Added: 0022096
2009-11-23 12:29networkbNote Added: 0022106
2009-11-23 12:29networkbPriorityurgent => immediate
2009-11-23 12:45rafarodaNote Added: 0022108
2009-11-24 09:38rafarodaNote Added: 0022130
2009-11-24 09:38rafarodaProposed Solution updated
2009-11-24 09:38rafarodaSteps to Reproduce Updated
2009-11-27 09:21dmitry_mezentsevNote Added: 0022220
2009-11-27 12:14rafarodaNote Added: 0022224
2009-11-27 17:02rafarodaFile Added: C_DOCTYPE_TRL_es_ES_SCRIPT_ORA.txt
2009-11-27 17:03rafarodaNote Added: 0022226
2009-11-27 17:08rafarodaNote Added: 0022227
2009-11-27 17:08rafarodaPriorityimmediate => urgent
2009-12-17 08:58alostaleRelationship addedrelated to 0011798
2009-12-30 18:44psarobeRelationship replacedhas duplicate 0011798
2010-01-21 12:25rafarodaRelationship addedrelated to 0012020
2010-01-21 12:47rafarodaRelationship replacedhas duplicate 0012020
2010-02-18 18:26adrianromeroIssue cloned0012348
2010-02-18 18:26adrianromeroRelationship addedrelated to 0012348
2010-02-18 18:26adrianromeroStatusacknowledged => scheduled
2010-02-18 18:26adrianromerofix_in_branch => pi
2010-02-18 18:27adrianromeroNote Added: 0024613
2010-02-18 18:27adrianromeroStatusscheduled => closed
2010-02-18 18:27adrianromeroResolutionopen => no change required
2010-02-19 00:00anonymoussf_bug_id0 =>
2010-03-10 13:33rafarodaNote Added: 0025210
2010-03-10 18:28anonymoussf_bug_id => 2967934

Notes
(0021213)
shuehner   
2009-10-20 15:59   
Which version of the spanish translation pack module was used?

I think some versions did not include the ad_ref_list translation which could lead to this issue.
(0021216)
networkb   
2009-10-20 16:13   
I am using spanish localization pack 1.0.4
(0021237)
rafaroda   
2009-10-21 07:55   
Víctor,

Can you please comment on this issue?

Thanks.
(0021251)
vmromanos   
2009-10-21 10:46   
(edited on: 2009-10-21 10:47)
Rafa,

Yesterday I was talking to Stefan about this issue, maybe he can explain better where the problem is.


The summary is:
The doc types are translated into Spanish in the AD_REF_LIST_TRL_es_ES.xml file (example line 1008 of the 1.0.4 version). So the problem is in the import language procedure.

The key is the related bug 0007204. C_doctype and C_paymentterm depend on the client, and the import language doesn't manage the tables that are per client.

The problem is data that depend on a client may change between clients, so what should we do? Should we always overwrite the user data with the XML content? Should we keep the data?

We should take a decision about how the import language process should behave and implement it.

This is not a translation bug, but a bug in the design of the import language process.
(0021265)
rafaroda   
2009-10-21 12:33   
Solution proposed needs to be discussed within the Platform team.
(0021711)
networkb   
2009-11-11 10:17   
Any update on this?
(0021863)
dmitry_mezentsev   
2009-11-16 15:43   
Hi Guys,

What is the status or decision here?

Thanks.
(0021944)
rafaroda   
2009-11-18 09:15   
According to Asier:
"The conclusion we have now is. Document type currently are inserted hardcoded by Initial Client Setup, they should be inserted by a new Client dataset in core, translations for them should be managed by a dataset included in the localization pack. The problem would be for users that are currently working because these new dataset would be offered for those clients as they are not installed in them, this is not correct because when trying to install the dataset, it would fail trying to insert duplicate data. The solution would be to add a postcript for the update that inserts for existent client data in ad_ref_data_loaded table setting the new dataset as installed, this is blocked till postscripts for modules are implemented (issue 0011247). Furthermore, currently there are triggers that populate *_trl tables, the problem is that existent document types have entries in their trl tables, and this would conflict when trying to install the translation trl. The solution would be to remove these translations in the mentioned postscript and to remove for non core elements."
(0021946)
rafaroda   
2009-11-18 09:19   
Downgraded to Urgent because is blocked by feature request 0011247.
(0021948)
alostale   
2009-11-18 09:24   
The workarround would be to create a sql script for these cases. This script would populate the trl tables and should be executed per client in the instance.
(0022096)
dmitry_mezentsev   
2009-11-23 10:49   
Hi Rafa,

Could you please provide update on this issue? We discussed that Priority was changed not transparent (are we going to return it back) and if so what are our next steps (cause Issue is very hot then)?

Thanks.
(0022106)
networkb   
2009-11-23 12:29   
I agree with alostale in the proposed solution for the currently partners
(0022108)
rafaroda   
2009-11-23 12:45   
In order to satisfy the customer needs please provide (attach to the issue):
1) The dataset
2) The postscript

This issue remains as immediate until these components are provided.

Thanks.
(0022130)
rafaroda   
2009-11-24 09:38   
Does not apply to payment terms, only to document types.
(0022220)
dmitry_mezentsev   
2009-11-27 09:21   
Hi Rafa,

Eduardo is on holidays for several day but the issue is still open.

Can we try to tackle it without him?
(0022224)
rafaroda   
2009-11-27 12:14   
Translations into es_ES of the Document Types generated by the Initial Client Setup can be found at http://spreadsheets.google.com/ccc?key=0AohY6-U9-FFVdHREQzRmRGtaMXVCSkZnRHcyZ1ludUE&hl=es [^] ("deprecated" document types will be left in English).

The SQL script to update these labels inside the C_DOCTYPE_TRL table will be provided in a few hours.
(0022226)
rafaroda   
2009-11-27 17:03   
Please find attached the script for Oracle to populate the Spanish records of C_DOCTYPE_TRL table.
(0022227)
rafaroda   
2009-11-27 17:08   
Issue has been downgraded to Urgent now that script has been provided, waiting until feature request 0011247 is resolved.
(0024613)
adrianromero   
2010-02-18 18:27   
A solution has been sent to the partner and a new feature request has been created to track the issue.
(0025210)
rafaroda   
2010-03-10 13:33   
See feature request @ 0012348