Open Bug 835074 Opened 11 years ago Updated 2 years ago

Add localizable language names to Firefox: Mari (chm), Komi-Permyak (koi), Komi (kom), Komi-Zyrian (kpv), Moksha (mdf), Meadow Mari (mhr), Hill Mari (mrj), Erzya (myv), Udmurt (udm)

Categories

(Core :: Internationalization, defect)

defect

Tracking

()

People

(Reporter: unghost, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached patch Patch v 1.0Splinter Review
FU-lab team (http://code.google.com/p/fu-lab/downloads/list) has asked my help with creating Komi and Udmurt spellcheck dictionaries for Firefox. I found out that Firefox doesn't recognize Udmurt language code and recognize only "kv" language code for Komi."kv" is macrolanguage code, which shouldn't be used for dictionaries.
Following patch adds support for these languages and several other languages, which dictionaries will be created by FU-lab team in future.
Attachment #706808 - Flags: review?(smontagu)
Attachment #706808 - Flags: review?(l10n)
Attachment #706808 - Flags: review?(smontagu) → review+
Blocks: 793881
Axel, review ping?
Comment on attachment 706808 [details] [diff] [review]
Patch v 1.0

Sorry, but we really need a solution here that scales, we can't continue to grow and grow this list.

Is there any reason why we can't make the dictionary plugins support all the meta data here?
Attachment #706808 - Flags: review?(l10n) → review-
(In reply to Axel Hecht [:Pike] from comment #2)
> Comment on attachment 706808 [details] [diff] [review]
> Patch v 1.0
> 
> Sorry, but we really need a solution here that scales, we can't continue to
> grow and grow this list.

Is there any problem with rate of expansion of this list? Looking at http://hg.mozilla.org/mozilla-central/filelog/29dd80c95b7d/toolkit/locales/en-US/chrome/global/languageNames.properties I see that there were no additions in this list in 2010-2011 and only 4 languages have been added in 2012.
I don't think that it's much problem for localizers.
FWIW, I can drop from patch Komi (kom) and Mari (chm) - which are macrolanguage codes, not suitable for dictionaries.
For the record, most of these languages were already part of the list in bug 716321. As explained in bug 716321 comment 12, they were likely included in the list because spellchecker communities exist for them.

(In reply to Axel Hecht [:Pike] from comment #2)
> Sorry, but we really need a solution here that scales, we can't continue to
> grow and grow this list.

There are other places where we have attempted to discuss such a solution (e.g. bug 666662), but the discussions have not made much progress.

It does not make much sense to hold up or discriminate against new communities that are already in existence while we sort out what to do about the ones that might be in the future.

There is no real way around continuing to expand this list until we sort out a better way to handle languages in general. Right now, the proposed list already only includes languages that have existing communities or that are commonly supported on the Internet already.

> Is there any reason why we can't make the dictionary plugins support all the
> meta data here?

It's not clear to me what metadata you're referring to or how it would be supported by dictionary plugins.
Depends on: 716321
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: