Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-16 Thread Charles de Miramon
Le Dimanche 16 Février 2003 20:03, Hendrik Sattler a écrit : > > Hmm, not practical at all, since root does not have the same locale(s) as > all users and the locale package is no base package. why, if I am root with a French locale ? apt-get install koffice will install koffice and the French i1

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-16 Thread Hendrik Sattler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 16. Februar 2003 16:27 schrieb Charles de Miramon: > Another point of view would be to push Debian to have a global solution for > translation packages and have some intelligence in apt so that apt-get > install koffice will install automat

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-16 Thread Charles de Miramon
Le Samedi 15 Février 2003 14:04, Ben Burton a écrit : > > If koffice-i18n is packaged as a single massive binary package, it means > that as (say) a German speaker, I'd have to download what appears to be > at least 8 megabytes worth of i18n package just to get my 200k of German > translations. An

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-15 Thread Matthieu Robin
Le Samedi 15 Février 2003 14:04, Ben Burton a écrit : > If koffice-i18n is packaged as lots of little language-specific > packages, it means we have lots more little packages in debian that add > to the already confusing number of packages for users to choose from and > for slow hardware to deal wi

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-15 Thread Matthieu Robin
Le Samedi 15 Février 2003 14:04, Ben Burton a écrit : > If, however, we (the developers) can go to the extra hassle of combining > the koffice and core KDE i18n files I suppose you mean the maintainer(s)... So they would have to remove the koffice i18n files in KDE_x_y_BRANCH (I still don't under

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-15 Thread Ben Burton
> I'll try to explain my point of view on koffice-i18n. It's very simple: if we > have kde and koffice (separate) packages, with different release cycles and > so, why should we package koffice-i18n and kde-i18n together? You're right, it's a bad solution. The problem is that the other solutio

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-15 Thread Juan Manuel GarcÃa Molina
Hi, folks. I'll try to explain my point of view on koffice-i18n. It's very simple: if we have kde and koffice (separate) packages, with different release cycles and so, why should we package koffice-i18n and kde-i18n together? Well, I have just take the same philosophy of work from Noel and kde

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-14 Thread Ben Burton
> I agree that this should be taken up-stream to ask KDE to keep the > languages seperate and merge koffice and kde together. I think it will be difficult to persuade upstream to supply KDE and KOffice i18n stuff together, since KDE and KOffice are on different release cycles. However, from the

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-14 Thread John Gay
I would recommend going with the i18n-foo packages and trying to keep the koffice and kde stuff merged and synced. This way, someone can fetch and install the language they want without needing to install ALL languages. And the merging would at least cut the number of different packages in half.

Re: Bug#181009: ITP: koffice-i18n -- i18n files for koffice

2003-02-14 Thread Ben Burton
> * Package name: koffice-i18n Hi. The situation with koffice i18n stuff is a bit unclear; in particular, it has been included in kde-i18n at various times in the past, though it doesn't seem to be at the moment. There was a short thread on debian-kde regarding koffice i18n stuff (http://li