That's a bigger effort. I'd rather consider using CLDR 2.0, fixing the few problems you have in the data, and then regenerate it using the python scripts.
Cheers, Lars On Dec 10, 2012, at 12:38 PM, El Mehdi Fekari <[email protected]> wrote: > Is it also possible to updated Qlocale data to CLDR 22.1 in Qt4.8.4? > > Thanks, > Mehdi > > On 12-12-10 6:19 AM, "Konstantin Ritt" <[email protected]> wrote: > >> QLocale data in Qt 5.0-rc1 is already up-to-date (generated from CLDR >> 22.1). >> >> Konstantin >> >> >> 2012/12/10 El Mehdi Fekari <[email protected]>: >>> Hi, >>> >>> We've got many issues concerning the current Qlocale data based on >>> CLDR v2.0. We currently have a critical bug concerning the default >>> numbering system Qlocale provides for some countries/region in the >>> BlackBerry10 product: >>> >>> * Qlocale (with CLRD2.0 Data) specifies native digits for most of >>> the Indic locales (Punjabi, Hindi, Tamil, Š), which supposed to be in >>> Latin digits ( fixed in CLRD 22.1). >>> * Qlocale provides Arabic digits for Slovak region. ( fixed in CLRD >>> 22.1) >>> >>> The most recent version of CLDR (22.1) is more consistent with the >>> current ICU and specifies correct default numbering system values. >>> >>> So I think the scripts qlocalexml2cpp.py and cldr2qlocalexml.py need to >>> be updated to support recent CLDR 22.1 and generate more recent data for >>> Qlocale. >>> >>> Cheers, >>> >>> Mehdi >>> >>> >>> --------------------------------------------------------------------- >>> This transmission (including any attachments) may contain confidential >>> information, privileged material (including material protected by the >>> solicitor-client or other applicable privileges), or constitute >>> non-public information. Any use of this information by anyone other than >>> the intended recipient is prohibited. If you have received this >>> transmission in error, please immediately reply to the sender and delete >>> this information from your system. Use, dissemination, distribution, or >>> reproduction of this transmission by unintended recipients is not >>> authorized and may be unlawful. >>> _______________________________________________ >>> Development mailing list >>> [email protected] >>> http://lists.qt-project.org/mailman/listinfo/development > > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
