adding all of iso639_3 to either en.xml or root.xml

[John Emmons]

Another potential problem here is that en.xml and iso639-3 don't always
agree 100% on the names.  Maybe in root - but I think it is definitely
going to be hard to maintain.
I put it on the agenda for the next TC mtg.


Regards,

John C. Emmons
Globalization Architect & Unicode CLDR TC Chairman
IBM Software Group
Internet: emmo at us.ibm.com




From:	"Mckenna, Mike" <mimckenna at paypal.com>
To:	Mark Davis ☕️ <mark at macchiato.com>
Cc:	Martin Hosken <martin_hosken at sil.org>, "cldr-users at unicode.org"
            <cldr-users at unicode.org>, "Steven R. Loomis"
            <srl at icu-project.org>
Date:	07/15/2014 10:30 AM
Subject:	Re: adding all of iso639_3 to either en.xml or root.xml
Sent by:	"CLDR-Users" <cldr-users-bounces at unicode.org>



I know we at PayPal would certainly be fans of getting all of iso639-3 in
CLDR. We are currently cobbling lists together in English and then
translating to target languages. I would have no problem with having the
English names in root since these and the French are the official ISO
entries.

We use the lists for pull-downs on postal address entry forms and need to
present them in user language for selection, local language for domestic
delivery and English for international postal mail.

Thanks,

Mike___

Sent from my iPhone

On Jul 14, 2014, at 11:56 PM, "Mark Davis ☕️" <mark at macchiato.com> wrote:

      I'm not sure it would be worth it. People can always pick up a copy
      of the language subtag registry and use it to back-fill.

      We do keep a copy of the registry in our tooling data directory, and
      that's what we do in our tooling, such as myCldrFile.getName
      (language).


      Mark

      — Il meglio è l’inimico del bene —


      On Tue, Jul 15, 2014 at 6:52 AM, Steven R. Loomis <
      srl at icu-project.org> wrote:
        If anything should be in en and not root.

        Wonder if it could go into seed/en or something.

        It's not in en right now because of translation burden. But I'd
        think we could set controls via coverage.

        En.xml is hand curated now, that would be another distinction.

        Steven

        Enviado desde nuestro iPhone.

        El jul 14, 2014, a las 9:47 PM, Martin Hosken <
        martin_hosken at sil.org> escribió:

              Dear All,

              I notice that en.xml only contains
              localeDisplayNames/languages/language entries for a subset of
              iso639-3. Is there a case for filling out the list based on
              iso639-3 reference names so that people don't have to
              fallback to data not in the CLDR? Or, given iso639 has these
              reference names, is there a case for putting them into the
              root. I realise it's a bit odd to put what amounts to English
              names into root.xml. OTOH these are the official reference
              names and so act as fallback for all languages, so perhaps it
              would be appropriate. I'm happy either way. But I think CLDR
              would benefit from having the complete reference name mapping
              of iso639-3 in it.

              Yours,
              Martin
              _______________________________________________
              CLDR-Users mailing list
              CLDR-Users at unicode.org
              http://unicode.org/mailman/listinfo/cldr-users

        _______________________________________________
        CLDR-Users mailing list
        CLDR-Users at unicode.org
        http://unicode.org/mailman/listinfo/cldr-users


      _______________________________________________
      CLDR-Users mailing list
      CLDR-Users at unicode.org
      http://unicode.org/mailman/listinfo/cldr-users
      _______________________________________________
      CLDR-Users mailing list
      CLDR-Users at unicode.org
      http://unicode.org/mailman/listinfo/cldr-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140715/07542e4e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140715/07542e4e/attachment.gif>