Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0013368 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Openbravo ERP] E. Translation | major | always | 2010-05-18 15:48 | 2010-10-25 10:44 | |||||||
| Reporter | networkb | View Status | public | |||||||||
| Assigned To | iciordia | |||||||||||
| Priority | urgent | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0013368: It should be possible to modify the translations applyied by a translation module. | |||||||||||
| Description | It should be possible to modify the translations applyied by a translation module. Right now is not possible to change the translation of some elements of the application in order to use a different word than the word used by the translation module. This changes should be packaged into a module or configscript. | |||||||||||
| Tags | dev-platform-quick-wins, Modularity | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0030724) rafaroda (developer) 2010-09-07 09:33 |
What is the workaround proposed that can maintain the changed translation after updates? |
|
(0030793) iciordia (manager) 2010-09-07 21:44 |
Rafa, theoretically it is possible to create a core translation pack including only the changes. Then the installation process would be to install first the standard translation pack and then customized one with your changes. Second installation should transparently overwrite the translations in the first translation pack. After updates of the standard translation pack you should reinstall the customized one. It might work-around the problem. Can you please test and confirm? Thanks, Ismael |
|
(0032166) egoitz (developer) 2010-10-25 10:43 |
What happens if there is published a new translation pack that translates elements that are not translated in your own transalation module? Are this translations removed after install own your translation module? There is not other way to customize translations? There are customer that want to change some translations, or that want to modify the help of the application so they need to change the translation. The export language process should compare the translations of core on the databse with the xml's As the export.config.script does in order to export a configscript to modify translations. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-05-18 15:48 | networkb | New Issue | |
| 2010-05-18 15:48 | networkb | Assigned To | => alostale |
| 2010-05-24 16:10 | alostale | Assigned To | alostale => iciordia |
| 2010-09-07 09:25 | rafaroda | Issue Monitored: rafaroda | |
| 2010-09-07 09:25 | rafaroda | Tag Attached: dev-platform-quick-wins | |
| 2010-09-07 09:26 | rafaroda | Tag Attached: Modularity | |
| 2010-09-07 09:33 | rafaroda | Note Added: 0030724 | |
| 2010-09-07 21:44 | iciordia | Note Added: 0030793 | |
| 2010-10-25 10:43 | egoitz | Note Added: 0032166 | |
| 2010-10-25 10:44 | egoitz | Issue Monitored: egoitz | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |