Right now no localisation files for ChatZilla and DOM Inspector are located in langenus.xpi, which makes it somewhat complicated to translate these packages, as well as it creates chaos between different localisations. This bug is about moving those files into langenus.xpi, to ease localisation process.

This bug is invalid for the same reason that bug 63508 is invalid.

Not going to do this. You can still put a l10n of chatzilla in your langfrFR.xpi, if you like, or create a new JAR file like chatzilla-fr-FR.xpi

(In reply to comment #1) > This bug is invalid for the same reason that bug 63508 is invalid. This bug might not be on the first priority to you, but it is not invalid. As you wrote in Bug 63508 Comment 5: > If it's hard to > make a lang. pack because of this, maybe that's a bug in the lang. pack design. Also, in the time of bug 63508 (comment 5), there was a Netscape version of Mozilla, which did not include ChatZilla. Now there is no Netscape browser, so those reasons do not apply.* Please, notice that this bug talks about langenus.xpi, rather than en-US.jar, and that allows more freedom for a solution. Because of this issue, when I install en-GB language pack, and uninstall en-US, I have a big frame in Mozilla, which states that there is a problem (bug #234599). This bug might also create confusion for the end-user, if we are going to be consistent and create new JAR files, as suggested in comment 2. This _is_ a serious issue, and it must be solved before Mozilla 2.0. Please, notice that this bug already has one vote (not from the reporter, i.e. not from me), in only one or two days. :-) Reopening bug for the above reasons.

Reassigning to dedicated reopener. Please submit a patch and ask for reviews if this is truly important to you.

Chatzilla/inspector/venkman are semi-independent extensions, and they are not updated/localized at the same pace as the app suite. I can say immediately that I will r- any patch to move the locale files into langenus/en-US jar files. I would be OK with a patch that separates the localization into a file inspector-us.jar; then other langpacks can include a file inspector-de.jar as desired.

Same goes for me. These are extensions and are not part of the core browser, so they must be completely self contained. It's not that this is a low priority, so much as this is just not going to happen. Ever. Even if someone else does the work. What about other extensions? Do you expect all of the locale files for extensions hosted by mozdev.org in en-US.jar too?

One option, which looks very neat to me, is to create new .xpi files in the default distribution, and move ./locale/* directory from each extension to these .xpi files. I.e. add new .xpi packages: langenus-chatzilla.xpi, langenus-inspector.xpi and langenus-venkman.xpi. I think, similar things should be done with MailNews, Composer and other components. I am going to create a new bug in a week if one does not already exist. Any comments are welcomed.

Changing summary from Move ./locale/* from chatzilla.jar, inspector.jar, venkman.jar into langenus.xpi to Move ./locale/* from chatzilla.jar, inspector.jar, venkman.jar into chatzilla-enus.xpi, inspector-enus.xpi, venkman-enus.xpi respectively (later to come: modularise langenus.xpi the same way)

This splits the chatzilla.jar file into two bits, chatzilla.jar for content/skin and chatzilla-enus.jar for locale stuff. It also adds stuff to the installer package lists, to make that work. Big problem here is that I couldn't see a way to make the en-US package be installed iff the main Chatzilla package was selected (since they are stuffed into two separate XPIs).

According to bsmedberg on IRC it should already work, but nevertheless, this was the change I made to make it work for me (if running it from the objdir is wrong, someone needs to document that :) ).

Little note about the former patch: I changed the .pkg file for Chatzilla as well as the existing packing files. I understand this is for the new packager, but as I couldn't get the PACKAGING_20030906_BRANCH to build, I can't test it.

Comment on attachment 143069 [details] [diff] [review] Adds Chatzilla-enus package Ok, looks like I missed the install.js stuff in here. Neither CZ package generated by this patch is likely to install. If the packager stuff wasn't in so many bits, I'd try to work it out, but I don't have time to learn another bit of it right now.

I am convinced this is not the way to go.

(In reply to comment #13) > I am convinced this is not the way to go. Could you please provide the reasons behind your decision? Thanks.

These are extensions, and extensions should have self-contained locales. We decided for aviary, and this decision will continue, that if extensions are localized they should contain the localization inline in the extension XPI, to avoid extensions-of-an-extension syndrome.