135740 - Investigate bundling all strings into single jar file

Status: RESOLVED WONTFIX

(Core :: Internationalization: Localization, enhancement)

Description

[dbragg]

There has been some discussion on the localization newsgroup (n.p.m.l10n) about
the difficulty of catching all the strings to make a fully localized build. 
Specifically the "optional" components like venkman, inspector, Chatzilla were
mentioned in the discussion.

This bug is to track investigation into the possibility/correctness of bringing
the strings from these modules into the "language" jar (i.e. en-US.jar) for easy
of localization.

Comment 1

[xspuente]

I think ALL localizable strings should be included under en-US.jar, whether they
are optional components or not. If a person would like to turn on or off
inspector, chatzilla or any other thing, he/she should have the opportunity to
have it displayed in the locale he or she has chosen.

Imagine that every single component has its associated localization. If we talk
about Mozilla, Venkman, Inspector, Chatzilla,... and we are talking right now of
about 60 different languages, that would make more than 240 files. A single file
for each language is the more convenient solution. Moreover, they don't
represent a lot of space (10-20 kb in a 500 kb langpack is not much).

On the other hand, this will also help to standarize the language packages that
are released, since all of them are quite different.

Comment 2

[tao]

new owner ->tao

Comment 3

[Karl Ove Hufthammer]

One problem is that the various components use different localeversions. E.g. in
Mozilla 1.0, DOM Inscpector uses 0.9.4. Therefore we can't bundle the
localization for all products in *one* file either, which makes installing
unncessary complicated.

Comment 4

[Karl Ove Hufthammer]

*** Bug 130813 has been marked as a duplicate of this bug. ***

Comment 5

[tao]

Hi, Bob: please reassign these i18n/l10n/l12y bugs accordingly. thx!

Comment 6

[Gordon P. Hemsley [:GPHemsley]]

Given how the l10n landscape has changed since this bug was filed, is this still a desired feature?

If not, this seems like a WONTFIX or WFM.

Comment 7

[Axel Hecht [:Pike]]

The bug as filed is kinda still valid for SeaMonkey, in particular, we haven't figured out how they should do chatzilla and such right.

But for our core technology, this is long solved, so it's a tie between wontfix and worksforme. Picked wontfix as we're not solving the optional-component piece in core for now.