[ 
https://issues.apache.org/jira/browse/OFBIZ-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharan Foga updated OFBIZ-5362:
-------------------------------
    Sprint: Bug Crush Event - 21/2/2015

> Create a periodic service to use ICU4J for updating i18n data
> -------------------------------------------------------------
>
>                 Key: OFBIZ-5362
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5362
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Priority: Minor
>              Labels: ICU4J, data, i18n
>
> This was proposed by Adrian in OFBIZ-5301, here is the (adapted) quote of our 
> comments:
> {quote}
> Jacques: There are no (yet) easy ways (as for countries) to check and 
> especially follow changes for other data like: languages, UOMs and currencies.
> Adrian: We can have the framework updating those. After the library is 
> updated, we can run a service that queries the library and updates the 
> database.
> Jacques: Actually I don't know much about ICU4J yet, but it seems it's worth 
> doing it then. Just that we will need also to backport in releases. This can 
> be done while updating ICU4J lib, say every 6 months or even when creating a 
> new release.
> On ICU4J updates, we would run this service based on updated ICU4J lib and it 
> will update the concerned data files (rather than DB BTW)
> For the countries, I wonder if it's worth it. Because the manual process I 
> thought about would take few minutes on every change. But as I explained the 
> 3166 newsletter exists, so far, only for countries. For other cases it's 
> harder to keep the data updated manually. You have to muck around in ISO 
> or/and wikipedia sites to fish the information.
> {quote}
> Please Adrian add any correction or information needed, thanks
> Here is a link for  ICJ4U: 
> http://www-01.ibm.com/software/globalization/icu/index.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to