Building a localised SeaMonkey 2.42

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
Hello,
I have successfully compiled SeaMonkey 2.42 from Dave Yeo's sources. Now I  
want to build a localised (German) version.
My plan is to
1. Download this  
https://hg.mozilla.org/releases/l10n/mozilla-release/de/rev/SEAMONKEY_2_46_RELEASE 
German locale tarball and the corresponding en-US one,
2. unpack the German tarball to D:\gecko45\locale_de and the en-US one  
anywhere else,
3. compare the files from the en-US 2.46 language pack with the ones from  
2.42 and edit the German ones so they are at the state of 2.42,
4. add mk_add_options MOZ_CO_LOCALES=de, ac_add_options  
--enable-ui-locale=de and
ac_add_options --with-l10n-base=/gecko45/locale_de to my mozconfig file,
5. build.

Can someone tell my if this will likely work? Are there any missing steps?  
Or is there an easier way to do this?

Many thanks,
Laurenz Sommer
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Frank-Rainer Grahl-3
 > Can someone tell my if this will likely work?
Likely not.

 > Are there any missing steps? Or
 > is there an easier way to do this?

 > 4. add mk_add_options MOZ_CO_LOCALES=de, ac_add_options
--enable-ui-locale=de and

These are all unsupported options. As long as everything is translated you
might get away with it but the official way is to set up l10n-merge.

Here are the steps for a 2.46 Windows build which you need to adapt:

https://pastebin.mozilla.org/9024487
Not sure if 2.42 needs other options. It is also affected by the l10n build
bug because of which Seamonkey needed to remove the extensions from the
distribution. Adrian Kalla has a workaround for it but it didn't work on the
offical builders.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1231349#c4

FRG

Laurenz Sommer wrote:

> Hello,
> I have successfully compiled SeaMonkey 2.42 from Dave Yeo's sources. Now I
> want to build a localised (German) version.
> My plan is to
> 1. Download this
> https://hg.mozilla.org/releases/l10n/mozilla-release/de/rev/SEAMONKEY_2_46_RELEASE 
> German locale tarball and the corresponding en-US one,
> 2. unpack the German tarball to D:\gecko45\locale_de and the en-US one
> anywhere else,
> 3. compare the files from the en-US 2.46 language pack with the ones from 2.42
> and edit the German ones so they are at the state of 2.42,
> 4. add mk_add_options MOZ_CO_LOCALES=de, ac_add_options --enable-ui-locale=de and
> ac_add_options --with-l10n-base=/gecko45/locale_de to my mozconfig file,
> 5. build.
>
> Can someone tell my if this will likely work? Are there any missing steps? Or
> is there an easier way to do this?
>
> Many thanks,
> Laurenz Sommer

_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Dave Yeo-3
Frank-Rainer Grahl wrote:

>> Can someone tell my if this will likely work?
> Likely not.
>
>> Are there any missing steps? Or
>> is there an easier way to do this?
>
>> 4. add mk_add_options MOZ_CO_LOCALES=de, ac_add_options
> --enable-ui-locale=de and
>
> These are all unsupported options. As long as everything is translated
> you might get away with it but the official way is to set up l10n-merge.
>
> Here are the steps for a 2.46 Windows build which you need to adapt:
>
> https://pastebin.mozilla.org/9024487

Is mozmake just gnumake?

> Not sure if 2.42 needs other options. It is also affected by the l10n
> build bug because of which Seamonkey needed to remove the extensions
> from the distribution. Adrian Kalla has a workaround for it but it
> didn't work on the offical builders.
> See https://bugzilla.mozilla.org/show_bug.cgi?id=1231349#c4

Dave

_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Frank-Rainer Grahl-3
Dave Yeo wrote:

> Frank-Rainer Grahl wrote:
>>> Can someone tell my if this will likely work?
>> Likely not.
>>
>>> Are there any missing steps? Or
>>> is there an easier way to do this?
>>
>>> 4. add mk_add_options MOZ_CO_LOCALES=de, ac_add_options
>> --enable-ui-locale=de and
>>
>> These are all unsupported options. As long as everything is translated
>> you might get away with it but the official way is to set up l10n-merge.
>>
>> Here are the steps for a 2.46 Windows build which you need to adapt:
>>
>> https://pastebin.mozilla.org/9024487
>
> Is mozmake just gnumake?

Yes. Just make under Linux.

FRG

_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
In reply to this post by Frank-Rainer Grahl-3
Frank-Rainer Grahl wrote:

> Here are the steps for a 2.46 Windows build which you need to adapt:
>
> https://pastebin.mozilla.org/9024487
> Not sure if 2.42 needs other options. It is also affected by the l10n
> build bug because of which Seamonkey needed to remove the extensions
> from the distribution. Adrian Kalla has a workaround for it but it
> didn't work on the offical builders.
> See https://bugzilla.mozilla.org/show_bug.cgi?id=1231349#c4
>
> FRG

Thanks for your reply. I will do my best to adapt your advice to OS/2
and SeaMonkey 2.42. I'd like to ask a few questions about it (sorry,
this the first time I build SeaMonkey from source):
First one general question: From what I understand from your steps I
have to build an English SeaMonkey first and the locale is added later.
Correct?
The mozconfig file for the locale only differs in the addition of
--with-l10n-base and I have to set LOCALE_MERGEDIR in my environment
settings?
May I set the additional mozconfig options in the beginning or is it
obligatory to build without them and then set them for the merge-de step?
The directory LOCALE_MERGE points to is just an empty working dir?

Laurenz
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Frank-Rainer Grahl-3
Laurenz Sommer wrote:
> First one general question: From what I understand from your steps I have to
> build an English SeaMonkey first and the locale is added later. Correct?

Yes. The compare-locales script uses the en-US package to check what is
missing in the locale package.

> The mozconfig file for the locale only differs in the addition of
> --with-l10n-base and I have to set LOCALE_MERGEDIR in my environment settings?

yes. l10n-base holds the local directories.

> May I set the additional mozconfig options in the beginning or is it
> obligatory to build without them and then set them for the merge-de step?

If you set them in the beginning en-US will pick them up which is not a good
thing.

> The directory LOCALE_MERGE points to is just an empty working dir?

yes. It will be created if there are missing locales and used to fill the gaps
with en-US strings.

This is more or less not well documented. I picked the steps from Adrian
Kallas unofficial build files.

FRG
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
Am 16.06.2017, 16:53 Uhr, schrieb Frank-Rainer Grahl <[hidden email]>:
> Yes. The compare-locales script uses the en-US package to check what is  
> missing in the locale package.
Does it only search for missing files or does it notice each missing  
strings?

I have adapted the whole language pack for 2.46 to 2.42 (I hope did not  
overlook something) and will begin to build later. I'll tell you when I  
have any results.
--

Laurenz
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
In reply to this post by Frank-Rainer Grahl-3
I followed the instructions as close as possible. First I got an error,
saying 'ECMAScript Internationalization API is not yet supported on this
platform' when I ran 'make configure' with the mozconfig file adjusted
for the localisation. I resolved this by editing build\autoconf\icu.m4
so it does not assume OS/2 does not support ECMAScript
Internationalization API (according to this
https://github.com/bitwiseworks/mozilla-os2/issues/101 OS/2 supports it)
and now treats it equal to WINNT. I'll attach the patch for this so one
can see the changes I made. I had to run autoreconfigure in
D:\gecko45\mozilla\intl\icu\source because
mozilla\intl\icu\source\configure interpreted the PATH environment
setting wrong.
But now 'make -f client.mk configure' terminates with the following
error: 'intl/icu/target> configure: error: Namespace support is required
to build ICU.' I attached the config.log created in
D:\gecko45\obj-sm\intl\icu\target.
Has anyone any idea how to resolve this problem? If I should provide
further information, please tell me.

Laurenz

_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2

Enable-ECMAScript-Internationalization-API-for-language-support.patch (838 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Dave Yeo-3
Laurenz Sommer wrote:

> I followed the instructions as close as possible. First I got an error,
> saying 'ECMAScript Internationalization API is not yet supported on this
> platform' when I ran 'make configure' with the mozconfig file adjusted
> for the localisation. I resolved this by editing build\autoconf\icu.m4
> so it does not assume OS/2 does not support ECMAScript
> Internationalization API (according to this
> https://github.com/bitwiseworks/mozilla-os2/issues/101 OS/2 supports it)
> and now treats it equal to WINNT. I'll attach the patch for this so one
> can see the changes I made. I had to run autoreconfigure in
> D:\gecko45\mozilla\intl\icu\source because
> mozilla\intl\icu\source\configure interpreted the PATH environment
> setting wrong.
> But now 'make -f client.mk configure' terminates with the following
> error: 'intl/icu/target> configure: error: Namespace support is required
> to build ICU.' I attached the config.log created in
> D:\gecko45\obj-sm\intl\icu\target.
> Has anyone any idea how to resolve this problem? If I should provide
> further information, please tell me.

I think on OS/2, you'll have to continue using the external icu
libraries or patch the internal libraries with whatever patches dmik
applied to the ones in http://trac.netlabs.org/ports/log/icu
Dave
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
Thanks, obviously the option 'ac_add_options --with-system-icu' was
missing in my mozconfig, so now I just used my normal mozconfig with
'ac_add_options --with-l10n-base=/gecko45/sm_locales' added. I reverted
my changes in mozilla\build\autoconf\icu.m4 and then the configure step
completed without errors. clobber-zip worked without problems, too, but
with merge-de compare-locales gives me strange results: It lists any
file in the subdirectorys of l10n-base followed by '// remove this
file'. It seems as it does not properly determine which locale files are
needed.

Just to make sure I'm not misunderstanding something: --with-l10n-base
points to the directory in which I have the subdirectory de which has
b2g, browser, calender, chat etc. as subdirectorys?

Can someone tell me what I have to do so compare-locales actually
compares the locales and not only suggests to remove necessary files?

Laurenz
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
Right after sending my last message I had the idea to try proceed
without the merge step. To save time I didn't create the whole browser
but a language pack with 'make langpack AB_CD=de'. This worked, although
sometimes I get an error, for example when I try to open the
preferences, caused by a missing translation. This proves that at least
the German locale files are in the right place but it also demonstrates
that I need compare-locales to find the missing translations.
So any help to get this working is still appreciated.

Laurenz
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Frank-Rainer Grahl-3
In reply to this post by Mozilla - OS/2 mailing list
Yes l10n-base points to the base directory for all the localés eg.
mylocales not mylocales\de

The build files append the language code and then use mylocales\de for
building in case of a de build.

FRG

Laurenz Sommer wrote:

> Just to make sure I'm not misunderstanding something: --with-l10n-base
> points to the directory in which I have the subdirectory de which has
> b2g, browser, calender, chat etc. as subdirectorys?
>
> Can someone tell me what I have to do so compare-locales actually
> compares the locales and not only suggests to remove necessary files?
>
> Laurenz

_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Building a localised SeaMonkey 2.42

Mozilla - OS/2 mailing list
Frank-Rainer Grahl schrieb:
> Yes l10n-base points to the base directory for all the localés eg.
> mylocales not mylocales\de
>
> The build files append the language code and then use mylocales\de for
> building in case of a de build.

Thanks for this clarification. I have the suspicion that the reason for
compare locales to not find the right files is related to our OS/2
python port because I zipped all locales directories and unzipped them
on my Debian, where I executed compare-locales, which worked flawlessly
and told me which translations are missing. When I ran the exact same
command in OS/2 it told me to delete all files from the localisation :S.

I added the missing translations and executed make installers-de, but I
got an other error (besides the one in the linked bug report for which I
applied Adrian Kalla's hack): When [hidden email] gets
packaged, I get an error like 'Error: Can't add
inspector/content/inspector/extensions/titledSplitter.css: inspector is
a file' for each file of inspector. Has someone a clue what might be the
reason for this?

Anyway, I have at least a German language pack so it is not that crucial
for me to build a fully localised SeaMonkey package. But if someone has
an idea to solve the problem I described above I'm still interested.

Thank you very much to all who helped me so far!

Laurenz
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2