Firefox translation - cvs and xpi
Eduardo Trápani
I've succesfully translated Firefox using the source tarball but I cannot expect all testers to build Firefox (on ppc I cannot even do it myself)
That's why I'd like to distribute the language.xpi for each platform.
Is there a 'make something' to create them?
I laso tried to get the en-US.xpi as a basis, but I can only find it in the Windows release[1], not in the other platform's [2][3] folders. Is the windows xpi sort of universal and I can expect it to work with the others?
Thanks, Eduardo.
[1] http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.6/win32/xpi/
[2] http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.6/linux-i686/xpi/
[3] http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.6/mac/xpi/
Axel Hecht
> Hi,
>
> I've succesfully translated Firefox using the source tarball but I
> cannot expect all testers to build Firefox (on ppc I cannot even do it
> myself)
>
> That's why I'd like to distribute the language.xpi for each platform.
>
> Is there a 'make something' to create them?
>
> I laso tried to get the en-US.xpi as a basis, but I can only find it in
> the Windows release[1], not in the other platform's [2][3] folders. Is
> the windows xpi sort of universal and I can expect it to work with the
> others?
The language packs are intended to work on all platforms, the make
process to create one is at
http://developer.mozilla.org/en/docs/Creating_a_Language_Pack
Axel
Eduardo Trápani
> process to create one is at
>
> http://developer.mozilla.org/en/docs/Creating_a_Language_Pack
Great, thanks a lot! There is something I don't understand though, in order to create the language pack I had to manually copy files to extensions/reporter/locales/eo because make langpack-ab was not picking them up.
Is that supposed to be so, are there any more files I should copy? Since I'm getting ready to send the zip file to ask for l10n-approval I'd like to know if I did right.
More info below. Thanks, Eduardo.
=======
On top of an original source tarball, say 1.5.0.6, I get client.mk and tools/l10n/l10n.mk
Then I follow these steps [1] and the l10n directory is created as mozilla's sibling, with eo inside. Then I add the already translated files from extensions/reporter, with the same structure they had in l10n/en-US.
But when I want to create the language pack I get an error about a missing eo/chrome/reportWizard.dtd, even though the file is inside l10n/eo/extenstions/...
make[2]: Entering directory `/home/edu/traduki/src/firefox/1.5.0.6/mozilla/extensions/reporter/locales'
+++ making chrome /home/edu/traduki/src/firefox/1.5.0.6/mozilla/extensions/reporter/locales => ../../../dist/xpi-stage/locale-eo/chrome/eo.jar
error: file './eo/chrome/reportWizard.dtd' doesn't exist at ../../../config/make-jars.pl line 443, <STDIN> line 11.
[1] http://developer.mozilla.org/en/docs/Create_a_new_localization
Michael Wolf
>
> But when I want to create the language pack I get an error about a
> missing eo/chrome/reportWizard.dtd, even though the file is inside
> l10n/eo/extenstions/...
>
> make[2]: Entering directory
> `/home/edu/traduki/src/firefox/1.5.0.6/mozilla/extensions/reporter/locales'
> +++ making chrome
> /home/edu/traduki/src/firefox/1.5.0.6/mozilla/extensions/reporter/locales
> => ../../../dist/xpi-stage/locale-eo/chrome/eo.jar
> error: file './eo/chrome/reportWizard.dtd' doesn't exist at
> ../../../config/make-jars.pl line 443, <STDIN> line 11.
Hi Eduardo,
It' the wrong path. The file reportWizard.dtd belongs to the reporter
tool. The locale files for this tool component are in the subfolder
reporter. The exact hierarchy in the eo.jar must be
chrome/eo/locale/eo/reporter
Extract the en-US.jar and you will see it.
So the reportWizard.dtd isn't missing but in the wrong folder only.
Korajn salutojn
Axel Hecht
>> The language packs are intended to work on all platforms, the make
>> process to create one is at
>>
>> http://developer.mozilla.org/en/docs/Creating_a_Language_Pack
>
> Great, thanks a lot! There is something I don't understand though, in
> order to create the language pack I had to manually copy files to
> extensions/reporter/locales/eo because make langpack-ab was not picking
> them up.
>
> Is that supposed to be so, are there any more files I should copy?
> Since I'm getting ready to send the zip file to ask for l10n-approval
> I'd like to know if I did right.
> More info below. Thanks, Eduardo.
Reporter is different, at least on the 1.5.0.x branch still. Sad, but
true. I suggest you keep the files in extension/reporter for review, as
that is where the files are supposed to be for the 1.8 branch, or
firefox 2.
It might be interesting for you that we don't plan to take new locales
for 1.5.0.x and expect new locales to be added on the 2.0 series.
Depending on the timing, I wouldn't expect that to happen before the
first minor update to 2.0, at least.
As 2.0 is string frozen, you should be good enough to get that tested,
too, RC1 is not far out, b2 is well out the door.
Axel
Michael Wolf
>
> Reporter is different, at least on the 1.5.0.x branch still. Sad, but
> true.
No, the locale files for Reporter are already on FF 1.5. in en-US.jar.
Axel Hecht
> Axel Hecht napisa:
> >
>> Reporter is different, at least on the 1.5.0.x branch still. Sad, but
>> true.
>
> No, the locale files for Reporter are already on FF 1.5. in en-US.jar.
>
Just that nobody cares about where they are in en-US.jar. It's how they
get there, and reporter is different in that respect.
Axel