Use CLDR data to assist l10n of language subtags

NEW
Unassigned

Status

()

Core
Localization
--
enhancement
7 years ago
5 months ago

People

(Reporter: GPHemsley, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bcp47], URL)

(Reporter)

Description

7 years ago
As we improve BCP 47 support, we'll begin to have an unwieldy list of language and region subtags to localize. Many of these have already been localized in CLDR and it would save localizers time and effort to be able to cull this information automatically.

I don't know if this should happen before, after, or independent of bug 666662, but I figured I should at least open a separate bug to discuss it.
(In reply to Gordon P. Hemsley [:gphemsley] from comment #0)
> As we improve BCP 47 support, we'll begin to have an unwieldy list of
> language and region subtags to localize. Many of these have already been
> localized in CLDR and it would save localizers time and effort to be able to
> cull this information automatically.
> 
> I don't know if this should happen before, after, or independent of bug
> 666662, but I figured I should at least open a separate bug to discuss it.

Can you please describe how CLDR data could help localizers to localize languages and region subtags? I've followed to http://cldr.unicode.org/ and I'm a bit lost how to proceed further. Where can I find list of languages and region subtags localized in some language?
Grab the core.zip from http://unicode.org/Public/cldr/2.0.0/, and then the interesting files with language names are are in main.

Note that CLDR would never overrule the decisions on the side of the mozilla community.
This may be now a dupe of bug 1431324 where we're investigating pipeline to get CLDR data directly into our localization resources.
You need to log in before you can comment on or make changes to this bug.