[
https://issues.apache.org/jira/browse/OFBIZ-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551047
]
Jeroen van der Wal commented on OFBIZ-1442:
-------------------------------------------
Hi Adrian,
I've worked on some huge applications which required localization and I think
localization of Ofbiz (also huge) should follow roughly the same process:
1. import all translatable files into a translation tool (could be an online or
offline tool);
2. let the tool build a glossary of all the terms within those files;
3. manualy tanslate and review all glossary items (can be done by
non-developers);
4. build localized files using the glossary;
When a new localized version of Ofbiz is needed the process starts over again
but the glossary is reused so only changed or untranslated items pop up.
A proper and consistent translation cannot do without tooling and should not
bother the developers. In my opinion a translation should be a separate package
managed by a separete team. I still don't see how your solution could avoid
missing property translations. Also, adding a new localizations will be a
painstaking process. I'm willing to put some time and effort to investigate in
tooling for Ofbiz translations but don't want to see my options limited to none
when all translations are being put in a single file.
> Add ability to use XML property files for locale-specific properties
> --------------------------------------------------------------------
>
> Key: OFBIZ-1442
> URL: https://issues.apache.org/jira/browse/OFBIZ-1442
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Adrian Crum
> Priority: Minor
> Attachments: xml_props.patch, xml_props.patch, xml_props_demo.patch
>
>
> As per discussion on the dev mailing list, implement XML property files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
