Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] E. Translationmajoralways2009-10-20 15:342010-03-10 18:28
ReporternetworkbView Statuspublic 
Assigned Toeduardo_Argal 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50MP9
OSLinux 64 bitDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product Version2.50MP6SCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0011051: 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
TagsNo tags attached.
Attached Filestxt file icon C_DOCTYPE_TRL_es_ES_SCRIPT_ORA.txt [^] (5,554 bytes) 2009-11-27 17:02 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0007204 newjonalegriaesarte Localization Pack: Spain DocType translation to spanish 
related to feature request 0010506 scheduledTriage 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 newiciordia Openbravo ERP Support for Business Objects Translations 
depends on feature request 0011247 closediciordia Openbravo ERP Add capability to modules to execute postScripts 
has duplicate defect 00117982.40MP14 closededuardo_Argal Openbravo ERP c_doctype elements are not translated after installing Spanish(Spain) translation in the application 
has duplicate defect 00120202.40MP15 closededuardo_Argal Openbravo ERP Some Document Types are still missing in the translation script. 
related to feature request 0012348 neweduardo_Argal Openbravo ERP Some lists are not correctly translated using spanish localization pack 

-  Notes
shuehner (administrator)
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.

networkb (developer)
2009-10-20 16:13

I am using spanish localization pack 1.0.4
rafaroda (developer)
2009-10-21 07:55


Can you please comment on this issue?

vmromanos (manager)
2009-10-21 10:46
edited on: 2009-10-21 10:47


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.

rafaroda (developer)
2009-10-21 12:33

Solution proposed needs to be discussed within the Platform team.
networkb (developer)
2009-11-11 10:17

Any update on this?
dmitry_mezentsev (developer)
2009-11-16 15:43

Hi Guys,

What is the status or decision here?

rafaroda (developer)
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."
rafaroda (developer)
2009-11-18 09:19

Downgraded to Urgent because is blocked by feature request 0011247.
alostale (manager)
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.
dmitry_mezentsev (developer)
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)?

networkb (developer)
2009-11-23 12:29

I agree with alostale in the proposed solution for the currently partners
rafaroda (developer)
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.

rafaroda (developer)
2009-11-24 09:38

Does not apply to payment terms, only to document types.
dmitry_mezentsev (developer)
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?
rafaroda (developer)
2009-11-27 12:14

Translations into es_ES of the Document Types generated by the Initial Client Setup can be found at [^] ("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.
rafaroda (developer)
2009-11-27 17:03

Please find attached the script for Oracle to populate the Spanish records of C_DOCTYPE_TRL table.
rafaroda (developer)
2009-11-27 17:08

Issue has been downgraded to Urgent now that script has been provided, waiting until feature request 0011247 is resolved.
adrianromero (manager)
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.
rafaroda (developer)
2010-03-10 13:33

See feature request @ 0012348

- Issue History
Date Modified Username Field Change
2009-10-20 15:34 networkb New Issue
2009-10-20 15:34 networkb Assigned To => rafaroda
2009-10-20 15:59 shuehner Note Added: 0021213
2009-10-20 15:59 shuehner Status new => feedback
2009-10-20 16:13 networkb Note Added: 0021216
2009-10-20 16:19 networkb Status feedback => new
2009-10-20 18:27 shuehner Relationship added related to 0007204
2009-10-21 07:55 rafaroda Note Added: 0021237
2009-10-21 07:55 rafaroda Assigned To rafaroda => vmromanos
2009-10-21 10:46 vmromanos Note Added: 0021251
2009-10-21 10:47 vmromanos Note Edited: 0021251
2009-10-21 12:33 rafaroda Note Added: 0021265
2009-10-21 12:33 rafaroda Assigned To vmromanos => alostale
2009-10-21 12:33 rafaroda Priority immediate => urgent
2009-10-21 12:33 rafaroda Status new => acknowledged
2009-11-02 10:41 networkb Target Version => 2.50MP9
2009-11-09 13:57 pnuding Priority urgent => immediate
2009-11-09 14:52 alostale Relationship added related to 0010506
2009-11-09 14:53 alostale Relationship added related to 0010876
2009-11-10 10:35 alostale Relationship added depends on 0011247
2009-11-10 10:48 alostale Assigned To alostale => eduardo_Argal
2009-11-11 10:17 networkb Note Added: 0021711
2009-11-16 15:43 dmitry_mezentsev Note Added: 0021863
2009-11-18 09:15 rafaroda Note Added: 0021944
2009-11-18 09:19 rafaroda Note Added: 0021946
2009-11-18 09:19 rafaroda Priority immediate => urgent
2009-11-18 09:24 alostale Note Added: 0021948
2009-11-23 10:49 dmitry_mezentsev Note Added: 0022096
2009-11-23 12:29 networkb Note Added: 0022106
2009-11-23 12:29 networkb Priority urgent => immediate
2009-11-23 12:45 rafaroda Note Added: 0022108
2009-11-24 09:38 rafaroda Note Added: 0022130
2009-11-24 09:38 rafaroda Proposed Solution updated
2009-11-24 09:38 rafaroda Steps to Reproduce Updated
2009-11-27 09:21 dmitry_mezentsev Note Added: 0022220
2009-11-27 12:14 rafaroda Note Added: 0022224
2009-11-27 17:02 rafaroda File Added: C_DOCTYPE_TRL_es_ES_SCRIPT_ORA.txt
2009-11-27 17:03 rafaroda Note Added: 0022226
2009-11-27 17:08 rafaroda Note Added: 0022227
2009-11-27 17:08 rafaroda Priority immediate => urgent
2009-12-17 08:58 alostale Relationship added related to 0011798
2009-12-30 18:44 psarobe Relationship replaced has duplicate 0011798
2010-01-21 12:25 rafaroda Relationship added related to 0012020
2010-01-21 12:47 rafaroda Relationship replaced has duplicate 0012020
2010-02-18 18:26 adrianromero Issue cloned 0012348
2010-02-18 18:26 adrianromero Relationship added related to 0012348
2010-02-18 18:26 adrianromero Status acknowledged => scheduled
2010-02-18 18:26 adrianromero fix_in_branch => pi
2010-02-18 18:27 adrianromero Note Added: 0024613
2010-02-18 18:27 adrianromero Status scheduled => closed
2010-02-18 18:27 adrianromero Resolution open => no change required
2010-02-19 00:00 anonymous sf_bug_id 0 =>
2010-03-10 13:33 rafaroda Note Added: 0025210
2010-03-10 18:28 anonymous sf_bug_id => 2967934

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker