Re: Packaging very large i18n material
On Mon, Jun 09, 2003 at 08:39:11PM +0200, Mathieu Roy <email@example.com> was heard to say:
> Nikolaus Rath <Nikolaus@rath.org> a tapoté :
> > Ben Burton <firstname.lastname@example.org> wrote:
> > > 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n).
> > >
> > > This is bad because we add another 37 binary packages to the archives.
> > > This is also not a solution that generalises since if we did this
> > > for every package in the archive that provides i18n files our package
> > > list would get completely out of hand.
> > I think this is the way to go. If this is done using a common naming
> > scheme, aptitude or dselect could hide all the localisation packages
> > and ask for the language to be used when selecting the binary package.
> Hum, it should be kept in mind that on some computer, several i18n are
> frequently used.
> It's bad to assume that the root preferences are fine for all users.
> So aptitude or dselect should, indeed, directly automatically select
> appropriate i18n packages, but hiding others ones is more
I don't think automatically hiding languages other than the ones
selected on an initial install would be a bad idea, as long as there was
a straightforward procedure for modifying them or unhiding other language
data. I'd say that in 99% of the cases I've seen, the languages needed for
a computer were known at install time. 
I don't really like the idea of using the name to store this
information, though. Couldn't we have a separate control field?
Cowardly escaping email for a week before anyone can reply,
 and 88% of all statistics are made up on the spot.
/-------------------- Daniel Burrows <email@example.com> -------------------\
| "He is so predictable, we could emulate |
| him with a two-state Turing Machine." |
\------- Listener-supported public radio -- NPR -- http://www.npr.org --------/