254728 - Localized firefox needs to register all chrome properly

Status: RESOLVED WONTFIX

(Core :: Internationalization: Localization, defect)

Description

[Oscar Manuel Gómez Senovilla]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7) Gecko/20040616

In the url, there are spanish firefox installers. It seems to happen to the last
firefox 0.9.x family, not sure if not platform dependant. The problem is that
those installers fail to create correctly a new profile. In
http://nave.hispalinux.org/productos/firefox/0.9/descargas/linux/ there's a 

Reproducible: Sometimes
Steps to Reproduce:
1. Make sure there's no firefox user profile 
2. Download and install any of the mentioned full installers
3. Execute firefox

Actual Results:  
There's an xul error in the lower part of the screen when creating the new profile.

Expected Results:  
Create the profile correctly

I think there's some issue with the help.jar, which isn't actually translated,
and the error mentions help.

I asked this some time ago in l10n newsgroup, and nobody answered, so this is
totally blocking for the spanish community.

Comment 1

[Oscar Manuel Gómez Senovilla]

Sorry, a mistake in the url

Comment 2

[Víctor Fernández]

I've found a way to create an installer avoiding this bug. I don't understand
why this works, but it does. You need to modify help.xpi:


1. Unzip it and edit install.js. Find the line:

   registerChrome(LOCALE  | DELAYED_CHROME, jarFolder, "locale/en-US/help/");

Replace "en-US" with your corresponding locale. In spanish it's:

   registerChrome(LOCALE  | DELAYED_CHROME, jarFolder, "locale/es-ES/help/");


2. Unzip "help.jar" inside "bin/chrome". Then enter the "locale" directory and
rename the directory "en-US" to your locale ("es-ES" in my case).

3. Go to "locale/<your-locale>/help" and edit contents.rdf replacing "en-US"
with your locale. In my case it's:


<?xml version="1.0" encoding="UTF-8"?>
<RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:chrome="http://www.mozilla.org/rdf/chrome#">

    <!-- Packages -->
    <RDF:Seq RDF:about="urn:mozilla:locale:root">
        <RDF:li RDF:resource="urn:mozilla:locale:es-ES"/>
    </RDF:Seq>

    <!-- Package Information -->
    <RDF:Description RDF:about="urn:mozilla:locale:es-ES">
        <chrome:packages>
            <RDF:Seq RDF:about="urn:mozilla:locale:es-ES:packages">
                <RDF:li RDF:resource="urn:mozilla:locale:es-ES:help"/>
            </RDF:Seq>
        </chrome:packages>
    </RDF:Description>

    <!-- Version Information -->
    <RDF:Description RDF:about="urn:mozilla:locale:es-ES:help"
        chrome:localeVersion="1.7"/>
</RDF:RDF>


4. Do the same with "content/help/chrome.rdf".
5. Repackage help.jar and help.xpi

Enjoy! :) I've needed to do the same with adt.xpi to make DOM Inspector work
correctly. I also recommend you to rename both help.xpi and help.jar to avoid
confusion with the original ones. If you do it, remember to edit install.js.

Comment 3

[Víctor Fernández]

Ooops! In the step 4 I wanted to say "content/help/contents.rdf".

Comment 4

[Oscar Manuel Gómez Senovilla]

Víctor: we should be able to use untranslated packages "as is", without having
to hack into them. Take that this happens for all extensions, and we can't go
hacking each and every foreign package that users want to use with non-US
installers.

Comment 5

[Víctor Fernández]

I agree but perhaps that gives some trace for the people at mozilla.org to fix
it. Also, it will be useful for other l10n teams _while the people at
mozilla.org fix it_. But it's obvious the resolution of this bug can't be made
by the l10n teams but by the Firefox developers.

Comment 6

[Martin Creutziger [:MMx]]

This is an issue for l10n that might be resolved soon due to the new l10n
procedure. Handing over to es-ES translator for triage.

Comment 7

[Oscar Manuel Gómez Senovilla]

Martin: please hold on the bug to the previous owner and don't assign to any
spanish maintainer, since I opened it myself. If you think somebody different
should own the bug, make sure it's not just the bug reporter nor anybody close
to him. :)

Comment 8

[Martin Creutziger [:MMx]]

well, I still think the error is in your installed-chrome.txt or elsewhere. If
you don't translate help, you have to register the english help or remove it
from the menu.
Furthermore, you have to include all the en-*.jar and US.jar for several
extensions to work right.

I hope that this issue will be resolved with the new CVS-based localizations
soon. Moving bug to l10n for now. bryner has enough work to do.

Comment 9

[Oscar Manuel Gómez Senovilla]

Bug 265445 did face the issue, and it's fixed, so I close this bug.

Comment 10

[Oscar Manuel Gómez Senovilla]

Bug 265445 is not fixed, though it claims to be. I've tried es-ES win32
installer from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9-l10n/ and
still shows this error.

Comment 11

[Oscar Manuel Gómez Senovilla]

Closed with boredom and now this is outdated and useless