How to build L10n XPI for SeaMonkey

Hi,

Someone has contacted me asking if I could prepare a XPI for 2.53.
I've more or less identified a changeset in l10n-central that I could
use (52657fcb764b), but I somehow tricked myself to write a dirty
script that walks through a 2.49.4 expanded XPI directory and seeks
each file there in the repository. This fails a number of times for
platform (win, mac, unix) directories, but I will move them by hand.

Only after having written that script I've come to think that there
must be an official way to build a L10n XPI. :-) I've found these
instructions:

https://developer.mozilla.org/en-US/docs/Mozilla/Creating_a_language_pack

but maybe for SeaMonkey there is more things to change that replacing
"browser" for "suite". Is there any other docs for me to follow that
better suits SeaMonkey (no pun intended)? ;-)

TIA

-- 
Proyecto NAVE (Mozilla es-ES Localization Team)
Mozilla Hispano Community
0
UTF
2/2/2019 7:05:50 PM
mozilla.dev.apps.seamonkey 1527 articles. 1 followers. Post Follow

4 Replies
98 Views

Similar Articles

[PageSpeed] 32

It is much easier in 2.57. 2.53 is still black magic.

Basically download the full patch queues from Bills site. Wait till later 
because I am pushing some backports which change strings today to gitlab. If 
you want direct access to my gitlab 2.53 patch queue repo just holler. This 
also contains an l10n-de patch queue if you want to see what is missing.

Because of our pet l10n bug 1231349 you need to apply a workaround Adrian 
suggested. It is for python/mozbuild/mozpack/packager/l10n.py and in 
PPPPPPP-frg-private-changes.patch.

I use two different configs for this:
..mozconfig.x6417enus more or less the standard config.


..mozconfig.x6417l10n disables the build environment and has the l10n-base

ac_add_options --with-l10n-base=d:/seamonkey/l10n/l10n-release
export LOCALE_MERGEDIR=d:/seamonkey/l10n/l10n-merge/253

Then you basically create your en-US build:

cp -p -f .mozconfig.x6417enus .mozconfig
mozmake -f client.mk configure
mozmake -f client.mk build
mozmake -C /d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32 
buildsymbols
mozmake -C /d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32 package
mozmake -C /d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32 installer

Now you need to set up merge and use the different l10n only config (example de):

cp -p -f .mozconfig.x6417l10n .mozconfig
export merge_dir="d:\\\\seamonkey\\\\l10n\\\\l10n-merge\\\\253"
LOCALE_MERGEDIR=d:/seamonkey/l10n/l10n-merge/253
mozmake -f client.mk configure
mozmake -C 
/d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32/suite/locales 
clobber-zip AB_CD=de
mozmake -C 
/d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32/suite/locales 
merge-de LOCALE_MERGEDIR=d:/seamonkey/l10n/l10n-merge/253
mozmake -C 
/d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32/suite/locales 
installers-de LOCALE_MERGEDIR=d:/seamonkey/l10n/l10n-merge/253
mozmake -C 
/d/seabuild/release/comm-release56-253/obj-x86_64-pc-mingw32/suite/locales 
langpack-de LOCALE_MERGEDIR=d:/seamonkey/l10n/l10n-merge/253

I wouldn't trust the installer cZ, DOMi and debugQA might be bad. Language 
pack for Lightning and SM is ok.

Just email me if you need more details or post a follow-up
FRG

Ricardo Palomares Martí­nez wrote:
> Hi,
> 
> Someone has contacted me asking if I could prepare a XPI for 2.53.
> I've more or less identified a changeset in l10n-central that I could
> use (52657fcb764b), but I somehow tricked myself to write a dirty
> script that walks through a 2.49.4 expanded XPI directory and seeks
> each file there in the repository. This fails a number of times for
> platform (win, mac, unix) directories, but I will move them by hand.
> 
> Only after having written that script I've come to think that there
> must be an official way to build a L10n XPI. :-) I've found these
> instructions:
> 
> https://developer.mozilla.org/en-US/docs/Mozilla/Creating_a_language_pack
> 
> but maybe for SeaMonkey there is more things to change that replacing
> "browser" for "suite". Is there any other docs for me to follow that
> better suits SeaMonkey (no pun intended)? ;-)
> 
> TIA
> 
0
Frank
2/3/2019 12:09:20 PM
Btw use l10n-release and the last 56 changeset you can find as a starting 
point. Later release now only use l10n-central but this one was still using 
l10n-release.

Ricardo Palomares Martí­nez wrote:
> Hi,
> 
> Someone has contacted me asking if I could prepare a XPI for 2.53.
> I've more or less identified a changeset in l10n-central that I could
> use (52657fcb764b), but I somehow tricked myself to write a dirty
> script that walks through a 2.49.4 expanded XPI directory and seeks
> each file there in the repository. This fails a number of times for
> platform (win, mac, unix) directories, but I will move them by hand.
> 
> Only after having written that script I've come to think that there
> must be an official way to build a L10n XPI. :-) I've found these
> instructions:
> 
> https://developer.mozilla.org/en-US/docs/Mozilla/Creating_a_language_pack
> 
> but maybe for SeaMonkey there is more things to change that replacing
> "browser" for "suite". Is there any other docs for me to follow that
> better suits SeaMonkey (no pun intended)? ;-)
> 
> TIA
> 
0
Frank
2/3/2019 12:13:31 PM
El 03/02/19 a las 13:09, Frank-Rainer Grahl escribió:
> It is much easier in 2.57. 2.53 is still black magic.

Thank you very much. Honestly, I don't understand most of your
explanations. :-) Let me ask you some specific questions:

- I'm trying to build just a langpack. Is it strictly needed to first
  get a full en-US installer, or am I misunderstanding you?
- Where is Bills site?
- Once I get the previous questions sorted out, I may be able to
  better understand the rest of your message (it's been a long time
  since I set up the build system and I'll have to look all of this
  in detail).

TIA

-- 
Proyecto NAVE (Mozilla es-ES Localization Team)
Mozilla Hispano Community
0
UTF
2/3/2019 8:18:55 PM
 > - I'm trying to build just a langpack. Is it strictly needed to first
 >    get a full en-US installer, or am I misunderstanding you?

You don't need a full installer but you need to use make package for en-US 
which is about more or less the same. So yes a full build is needed. The steps 
for doing the langpacks needs the en-US package and the merge needs to be 
executed against it.

 > - Where is Bills site?

http://www.wg9s.com/comm-253/

You need to import the patches or you language pack would be of not much use:

http://www.wg9s.com/comm-253/patches/git/mozilla-release/
http://www.wg9s.com/comm-253/patches/git/comm-release/


 > - Once I get the previous questions sorted out, I may be able to
 >    better understand the rest of your message (it's been a long time
 >    since I set up the build system and I'll have to look all of this
 >    in detail).
 >

If you want I can provide one in any language. Set up for "de" and just need 
to clone the other repos and find the right changeset.

Have build fun
FRG


Ricardo Palomares Martí­nez wrote:
> El 03/02/19 a las 13:09, Frank-Rainer Grahl escribió:
>> It is much easier in 2.57. 2.53 is still black magic.
> 
> Thank you very much. Honestly, I don't understand most of your
> explanations. :-) Let me ask you some specific questions:
> 
> - I'm trying to build just a langpack. Is it strictly needed to first
>    get a full en-US installer, or am I misunderstanding you?
> - Where is Bills site?
> - Once I get the previous questions sorted out, I may be able to
>    better understand the rest of your message (it's been a long time
>    since I set up the build system and I'll have to look all of this
>    in detail).
> 
> TIA
> 
0
Frank
2/3/2019 9:00:09 PM
Reply: