ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #07743
Re: Internationalizing scopes
On Mon, 2014-04-21 at 13:27 +0200, Martin Pitt wrote:
> Rodney Dawes [2014-04-17 11:41 -0400]:
> > And while it will help reduce the size to do that cleanup, it doesn't
> > fix the issue of how to upgrade them independently of the image itself,
>
> Why would we need to do that? We do image upgrades by far more often
> than we upgrade our langpacks, so it's not a problem at all to just
> fold the translation updates into the regular image updates.
Do the cleanup? Or upgrade langpacks independent of the image itself?
We're only shipping image updates far more often than langpacks
currently, because we're still under very early and heavy development.
We we start shipping on actual hardware, users aren't going to want to
install image updates every day, or even every few days. And no matter
how many image updates we ship, if the image doesn't include the
language the user needs, it's not going to solve that user's problem.
The cleanup we should do, because we aren't shipping brasero, metacity,
gedit, eog, nautilus, etc… on the image. But currently their
translations are being shipped there. How many MB will we gain back in
the image, if we pull the translations for all the things we aren't
shipping there? How many additional languages could we ship as a result
of that cleanup? Heck, there are lots of translations for things that
aren't even included in the default install of the ISO image, and
certainly not in the phone image. Like MoinMoin, git, or bacula.
> > or how to enable translations for other languages not on the image.
>
> Yes, that's hard to do as long as we have translations in .debs and
> system images aren't able to deal with those. But OTOH when we don't
> ship translations in langpacks but in the apps themselves, we don't
> have the option at all to enable/disable languages individually
> because we'd always ship with all of them.
Apps will certainly have their own translations in their own packages.
I'm talking about the system language. If the system translations aren't
available, it doesn't matter what translations are in the apps
themselves, because users will only be able to choose languages that are
included in the image already. With the current solution of having
langpacks on the image, we either have to ship them all, or get rid of
them and ship all the translations in their respective packages.
Follow ups
References
-
Re: Internationalizing scopes
From: Martin Pitt, 2014-04-16
-
Re: Internationalizing scopes
From: Rodney Dawes, 2014-04-16
-
Re: Internationalizing scopes
From: Martin Pitt, 2014-04-16
-
Re: Internationalizing scopes
From: Kyle Nitzsche, 2014-04-16
-
Re: Internationalizing scopes
From: Rodney Dawes, 2014-04-17
-
Re: Internationalizing scopes
From: Christian Dywan, 2014-04-17
-
Re: Internationalizing scopes
From: Kyle Nitzsche, 2014-04-17
-
Re: Internationalizing scopes
From: Rodney Dawes, 2014-04-17
-
Re: Internationalizing scopes
From: James Henstridge, 2014-04-17
-
Re: Internationalizing scopes
From: Rodney Dawes, 2014-04-17
-
Re: Internationalizing scopes
From: Martin Pitt, 2014-04-21