Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0009939 | Openbravo ERP | 09. Financial management | public | 2009-07-17 10:13 | 2009-07-23 13:51 |
|
| Reporter | networkb | |
| Assigned To | iciordia | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | scheduled | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.50MP2 | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0009939: Localization packs can include language translations for Fiscal Periods |
| Description | Spanish Localization Pack is installed, and the user is working in Spanish.
A new Fiscal year is created. Create periods process creates periods in English, although the application works with other language |
| Steps To Reproduce | Install a translation module (For example: Spanish Localization pack).
From now on, work with the new language installed.
Go to Financial management > Accounting > Setup > Fiscal Calendar > Year.
Create 2010 year.
Press "Create periods" process.
Go to Periods tab. All periods are in English. |
| Proposed Solution | Users can workaround this problem by editing Periods names to translate them to their local language. It should not be a big pain to do it once a year.
To develop this feature there are two different approaches:
1.- Make Fiscal Periods "translatable": Fiscal periods would have a translation so whenever this information is shown (windows, reports, etc.) it is translated to the user language. It allows translations to different languages within a Client.
It would require a change in core (high level effort estimation: 4 working days -> add trl support in model and modify reports and processes) and a change in each localization pack to include these translations (high level effort estimation: 0.5 working days for each localization pack)
2.- Make "Create Fiscal Periods" process to work in a specific language: base information for this process (months) are translated so the process generates Fiscal Periods in the language requested by the user. It means that Fiscal Periods are available in just one language within a Client.
It would require a change in core (high level effort estimation: 1 working day -> add trl support to ad_month and modify "Generate Periods" process) and a change in each localization pack to include these translations (high level effort estimation: 0.5 working days for each localization pack) |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0009271 | | closed | areefbasha | While creating Fiscal calendar Jan & Dec period are wrongly spelled as Ene & Dic | | related to | defect | 0002751 | 2.40 | closed | AinhoaPagola | Period's names built thorugh database function | | related to | defect | 0006187 | | closed | AinhoaPagola | Months has not been translated to Spanish |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-07-17 10:13 | networkb | New Issue | |
| 2009-07-17 10:13 | networkb | Assigned To | => rafaroda |
| 2009-07-20 16:57 | rafaroda | Note Added: 0018431 | |
| 2009-07-21 00:08 | psarobe | Status | new => scheduled |
| 2009-07-21 00:08 | psarobe | Assigned To | rafaroda => vmromanos |
| 2009-07-21 00:08 | psarobe | fix_in_branch | => pi |
| 2009-07-21 09:58 | vmromanos | Assigned To | vmromanos => rafaroda |
| 2009-07-21 09:59 | vmromanos | Note Added: 0018460 | |
| 2009-07-21 11:08 | rafaroda | Relationship added | related to 0009271 |
| 2009-07-21 11:09 | rafaroda | Relationship added | related to 0002751 |
| 2009-07-21 11:09 | rafaroda | Relationship added | related to 0006187 |
| 2009-07-21 12:58 | rafaroda | Note Added: 0018484 | |
| 2009-07-21 12:58 | rafaroda | Assigned To | rafaroda => alostale |
| 2009-07-21 12:58 | rafaroda | fix_in_branch | pi => |
| 2009-07-21 13:48 | alostale | Note Added: 0018487 | |
| 2009-07-21 13:48 | alostale | Assigned To | alostale => iciordia |
| 2009-07-23 13:51 | iciordia | Note Added: 0018590 | |
| 2009-07-23 13:51 | iciordia | Priority | immediate => normal |
| 2009-07-23 13:51 | iciordia | Type | defect => feature request |
| 2009-07-23 13:51 | iciordia | Summary | Periods are created in English although the user is working with other language => Localization packs can include language translations for Fiscal Periods |
| 2009-07-23 13:51 | iciordia | Steps to Reproduce Updated | |
|
Notes |
|
|
|
AD_MONTH_TRL values for es_ES are filled with English names:
select * from ad_month_trl where ad_language= 'es_ES' |
|
|
|
|
This bug has three bugs inside:
1- The first one is that the AD_MONTH_TRL table is not exported to XML. (See
Translation_data.xsql, method trlModulesTables).
2- The C_YearPeriod procedure doesn't use the AD_Month_TRL table for
generating the period, but the AD_Month table.
3- Due to the fact that the AD_MONTH_TRL is not exported, we can't translate
it into Spanish. |
|
|
|
|
Asier, could you please fix the first part of the issue then re-assign it to Victor?
1- The first one is that the AD_MONTH_TRL table is not exported to XML. (See
Translation_data.xsql, method trlModulesTables).
Thanks. |
|
|
|
|
There are 2 considerations about this issue:
-AD_Month_Trl is not exported because AD_Moth table is not part of modules. As it is instance data its translations are not exported (like M_Product ones, for example). We might consider whether this data should be in module.
-The other issue is how the period creation process should work. It inserts values in C_Period table, this table has not a TRL one, this means it can only have a single language. Therefore when creating the periods, which language should it use? I guess it shouldn't use the current session's one because if so, it could differ depending on the session. The solution might be the addition of a new C_Period_Trl table. |
|
|
|
|
This bug has been moved to feature request because Openbravo is working as expected: Fiscal Periods are not designed as translatable data so they are created in Openbravo base language for business information which is English. Openbravo standard multi-language support is for its user interface. Multi-language support for business information (products, business partner categories, Fiscal Periods, etc.) is a different requirement and needs to be solved as a different topic.
This feature can be prioritized by using Collaborative Development (sponsorship of features).
Ismael |
|