Re: CLDR errors that can't be corrected

From: Deborah Goldsmith (
Date: Wed May 17 2006 - 17:33:50 CDT

  • Next message: Philippe Verdy: "Re: CLDR errors that can't be corrected"

    On May 17, 2006, at 3:04 PM, Philippe Verdy wrote:
    > Given that vetting is only working now, it's strange that we have
    > not been given the opportunity to correct the obvious errors that
    > were in the CLDR (and during vetting, some items are marked in the
    > "Status Quo" (because there was "No Changes Proposed"), however
    > there has never been any opportunity to correct them since many
    > months (all propositions were said to be delayed, until the CLDR
    > opens again).
    > How to correct for example the errors that are still in the French
    > locale:
    > * duplicate currency names with the corrected currency names but
    > that conflict with another entry which is in "Status Quo".
    > * wrong "time/full/standard/standard" resource that can't be parsed
    > and create parsing errors in many other valid entries that are open
    > to corrections and whose votes indicate the correct parsable format.
    > * invalid inherited new resources for which there's not even any
    > translation.
    > How can we correct the items with the "Status Quo" when they do
    > conflict with other correct resources?

    Data submission was open in CLDR from February 3 through the end of
    March. Did you miss this announcement?

    > From:
    > Subject: Announcement: CLDR 1.4 Data Submission Period Now Starting
    > Date: February 3, 2006 9:04:13 AM PST
    > To:
    > Mountain View, CA, USA - 2006-02-03 - The Unicode Consortium today
    > announced the start of the submission period for locale and language
    > data for CLDR Version 1.4. The Common Locale Data Repository (CLDR)
    > project provides a general XML format for the exchange of language and
    > locale data for use in application and system development, and
    > gathers,
    > stores, and makes available a common set of language and locale data
    > generated in that format.
    > CLDR Version 1.3 contained data for 96 languages and 130
    > territories. In
    > addition to new data, CLDR 1.4 will add new structure to support,
    > among
    > other things: flexible date & time formatting (including quarters),
    > measurement system names, segmentation (customized line & word break),
    > and transliteration. For more information, see http://
    > During this period, the Unicode consortium encourages the
    > submission of
    > proposed new data and proposed corrections into the repository.
    > Most of
    > the data can be entered or viewed via the newly-revised Survey Tool at
    > An "Instructions" link on that
    > page
    > provides usage information.
    > At the end of the submission period (2006-03-15), there is a vetting
    > period for the submitted data. CLDR 1.4 is scheduled for release on
    > 2006-05-15.

    Vetting began at the beginning of May and runs through this Friday,
    May 19. During the vetting process, new data may not be submitted
    except by Expert vetters and CLDR Technical Committee members. Any
    proposed replacements for existing data in CLDR should have been
    entered using the survey tool between February 3 and March 30. In
    order for the process to be manageable, new data submission has to
    stop before the vetting process can begin.

    Note that the survey tool shows both the old data and the new data,
    and there may be multiple new proposals for a given data item. The
    conflicts are resolved through the vetting process.

    Do you have any specific examples of problematic data?

    Deborah Goldsmith
    Internationalization, Unicode liaison
    Apple Computer, Inc.

    This archive was generated by hypermail 2.1.5 : Wed May 17 2006 - 17:36:48 CDT