Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0004550 | Openbravo ERP | E. Translation | public | 2008-07-31 13:14 | 2008-11-25 23:22 |
|
Reporter | rafaroda | |
Assigned To | pheenan | |
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 20 | OS Version | Ubuntu 7.10 |
Product Version | pi | |
Target Version | 2.40 | Fixed in Version | pi | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0004550: Translation process does not take into account PO_ fields in Element window |
Description | 'Element' window has some fields with 'PO_' prefix. This is used for getting different names in purchase (PO) and sales (SO) windows for the same element (Remember that a window can be defined as a Sales or a Purchase window).
In English, this works correctly. If one goes to Goods Receipt (Procurement Management || Transactions || Goods Receipt || Header), the field label 'Purchase Order' displays but if one goes to Goods Shipment (Sales Management || Transactions || Goods Shipment || Header), the field label 'Sales Order' displays. In both cases, these labels point to the same Element record: C_Order_Id
In Spanish, even if the corresponding row (row id="558") inside AD_ELEMENT_TRL_es_ES.xml is well translated, both field labels display as 'Pedido de venta'. The same happens in row id="561" for 'Líneas pedido de compra' and 'Purchase Order Line'.
In some part of the translation process, this particularity is not taken into account. |
Steps To Reproduce | 1) Install the Spanish translation [1]
2) Login as 'Openbravo Admin' with language Spanish.
3) Go to 'Gestión de Compras || Transacciones || Albarán (Proveedor) || Cabecera': 'Pedido de venta' displays instead of 'Pedido de compra'
4) Go to 'Gestión de Compras || Transacciones || Factura (Proveedor) || Cabecera': 'Pedido de venta' displays instead of 'Pedido de compra'
5) Go to 'Gestión de Compras || Transacciones || Pedidos de compra cuadrados || Pedidos compra cuadrados': : 'Línea pedido de venta' displays instead of 'Línea pedido de compra'
[1] http://wiki.openbravo.com/wiki/Translating_Openbravo#Installing_a_new_translation [^] |
Proposed Solution | First, we need to know if it is a problem of the import translation process or during the compilation.
1) First see if it is an issue of the Import translation process. Run it and see in AD_ELEMENT_TRL table if PO_Name is 'Pedido de compra' and not 'Pedido de venta' when PO_Name of AD_ELEMENT is PO_Name = Purchase Order.
2) Compile the application and make the same check in the database.
|
Additional Information | |
Tags | No tags attached. |
Relationships | has duplicate | defect | 0004511 | | closed | rafaroda | Wrong PO label in Goods Receipt and Purchase Invoice Header | has duplicate | defect | 0002806 | 2.40 | closed | rafaroda | Labels ambiguos en "Pedidos de compra cuadrados" | blocks | defect | 0004442 | | closed | cromero | AD_WINDOW.ISSOTRX default value |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2008-07-31 13:14 | rafaroda | New Issue | |
2008-07-31 13:14 | rafaroda | Assigned To | => pheenan |
2008-07-31 13:14 | rafaroda | sf_bug_id | 0 => 2033751 |
2008-07-31 13:14 | rafaroda | OBNetwork customer | => No |
2008-07-31 15:19 | rafaroda | Relationship added | has duplicate 0004511 |
2008-07-31 15:20 | rafaroda | Relationship added | has duplicate 0002806 |
2008-08-04 19:43 | psarobe | Severity | minor => major |
2008-08-04 19:43 | psarobe | Status | new => scheduled |
2008-08-14 15:53 | jpabloae | Note Added: 0008560 | |
2008-08-18 11:18 | pheenan | Note Added: 0008577 | |
2008-08-18 11:27 | pheenan | Note Added: 0008578 | |
2008-08-18 20:24 | pheenan | Note Added: 0008604 | |
2008-08-21 13:35 | pheenan | Status | scheduled => resolved |
2008-08-21 13:35 | pheenan | Fixed in Version | => trunk |
2008-08-21 13:35 | pheenan | svn_revision | => 6445 |
2008-08-21 13:35 | pheenan | Resolution | open => fixed |
2008-08-21 13:35 | pheenan | Note Added: 0008650 | |
2008-08-21 13:44 | rafaroda | Note Added: 0008651 | |
2008-09-01 13:15 | cromero | Relationship added | blocks 0004442 |
2008-09-04 16:22 | psarobe | Target Version | => 2.40 |
2008-11-25 23:22 | psarobe | Regression testing | => No |
2008-11-25 23:22 | psarobe | Status | resolved => closed |
Notes |
|
|
Reminder sent to: pheenan The 2.40 release is close. As soon as all the major bugs are closed, we are ready to release. This is why I'd ask you to prioritize this issue. |
|
|
|
Import process has run successfully. Field PO_Name, and the other PO_ fields, are populated correctly with 'Pedido de compra' and the name field is populated with 'Pedido de venta'. This was checked following the compilation of the application.
Issue would appear to be in the compilation and rendering of the page. |
|
|
|
Have viewed the output of the UI following compilation and redeploy and this is only an issue with one field.
Pedidos compra cuadrados is the only screen now showing 'venta' instead of 'compra'. |
|
|
|
This problem does not appear to be anything to do with the AD_Element table or the application.
The issue is in the translations defined in the AD_FIELD_TRL xml file in the translations repository. If you look at row id 3318 in this table you will see that it is defined as
<value column="Name" original="Purchase Order">Pedido de venta</value>
This is the value that is used in presenting the user interface. I will fix this and commit to the translation repository for these fields.
There is nothing to be done in the openbravo erp application or code. |
|
|
|
Applied patch to check for null and empty PO_Name fields. |
|
|
|
|