>
> FRG, I've seen "l10n builds", and the problems with it, mentioned for years.
> *What is it* ?? A Real World language?? A Programming language?? What??
>
Basically all non en-US foreign language builds. Or your native language
build. Stricktly speaking en-US is an l10n build too but the master here and
building differently so we are not calling it l10n.
https://en.wiktionary.org/wiki/L10n
> But I'm guessing this would make the devs job a hell of a lot more difficult.
Not possible without modularized parts. And Firefox goes in a different
direction with what they call Gecko today. This more or and more becomes a
bloated mess mixing frontend browser parts with backend Gecko parts. Otherwise
it would be easier to stay current.
FRG
Daniel wrote:
Frank-Rainer Grahl wrote on 21/10/2018 8:56 PM:
They contain working versions of chatZilla, DOMi and Lightning. These should
be in the official builds too but we have problems with l10n builds.
FRG, I've seen "l10n builds", and the problems with it, mentioned for years.
*What is it* ?? A Real World language?? A Programming language?? What??
Still tracked in:
https://bugzilla.mozilla.org/show_bug.cgi?id=1231349
If you only do an en-US build this works fine. If you don't want calendar
you can disable or remove it in the add-on manager.
I've often thought that, rather than having to download the "whole Box and
Dice" package and then disable the undesired bits and pieces, perhaps, when I
want to upgrade, I should be asked which bits I want to download (say Browser,
M&N and addressbook ONLY whilst others might want M&N, Calendar and Chatzilla
ONLY), effectively making a package just for me and another, different,
package just for you, etc. In each case, the Core (Gecko??) would be
downloaded once, and the other bits added as needs be.
But I'm guessing this would make the devs job a hell of a lot more difficult.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
