Re: Building a localised SeaMonkey 2.42

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 [email protected] 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
[email protected]
https://lists.mozilla.org/listinfo/dev-ports-os2