Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0017431Openbravo ERPE. Translationpublic2011-05-31 10:342011-05-31 17:40
dalsasua 
marvintm 
immediatemajoralways
closedno change required 
20Ubuntu 10.10
2.50MP30 
 
OBPS
Core
No
0017431: Translation module with dataset at system level do not work
Spanish translation module do include now a dataset at system level, to translate the AD_MONTH table.
After installing attached module, where can be checked the existence of the dataset, months do have entries for es_ES language, but are not translated, according to the translation contained in the dataset
Install the attached module.
Re-Build system.
Go to Month window -> Translation tab.
Check that no month is translated.
Please also notice that: UOM, Countries and Currencies YES are translated, being also included in the same translation dataset.
No tags attached.
related to defect 0016129 closed ioritzCia Localization Pack: Spain Months are not translated into Spanish 
related to defect 0016128 closed ioritzCia Localization Pack: Spain Months are not translated into Spanish 
? org.openbravo.localization.spain.referencedata.translation.esES-1.1.4.obx (598,319) 2011-05-31 10:37
https://issues.openbravo.com/file_download.php?file_id=4130&type=bug
Issue History
2011-05-31 10:34dalsasuaNew Issue
2011-05-31 10:34dalsasuaAssigned To => alostale
2011-05-31 10:34dalsasuaModules => Core
2011-05-31 10:34dalsasuaOBNetwork customer => Yes
2011-05-31 10:35dalsasuaRelationship addedrelated to 0016129
2011-05-31 10:36dalsasuaRelationship addedrelated to 0016128
2011-05-31 10:37dalsasuaFile Added: org.openbravo.localization.spain.referencedata.translation.esES-1.1.4.obx
2011-05-31 10:45alostaleAssigned Toalostale => marvintm
2011-05-31 11:13dalsasuaIssue Monitored: ioritzCia
2011-05-31 17:40marvintmNote Added: 0037834
2011-05-31 17:40marvintmStatusnew => closed
2011-05-31 17:40marvintmResolutionopen => no change required

Notes
(0037834)
marvintm   
2011-05-31 17:40   
The problem here is that the module is not marked as "hasreferencedata". Therefore, the rebuild doesn't apply the system-level dataset which contains the translation information.

I've verified that once this is fixed, the translation rows for the c_month table are imported correctly, can be seen in the translation tab under the Month window, and are correctly used in the Fiscal Calendar window, when a period is created (its rows are created with Spanish names).