Adam Majer dijo [Thu, Jun 12, 2003 at 06:27:58PM -0500]:
> > The problem is that there is a *lot* of i18n material provided with
> > koffice. There are translations for 37 different languages, coming to a
> > total 21.7Mb.
> > 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n)
On Mon, Jun 09, 2003 at 11:46:18AM +1000, Ben Burton wrote:
>
> The problem is that there is a *lot* of i18n material provided with
> koffice. There are translations for 37 different languages, coming to a
> total 21.7Mb.
> 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n).
Dnia śro 11. czerwca 2003 23:41, David Pye napisał:
> KDE already groups languages (well kpersonalizer does ;)) as Eastern
> Europe, Western Europe, Asia, etc... Couldn't we compromise and have
> language packs similarly? ie I want Chinese, so I have to put up with
> koffice-i18n-asia, french koff
On Tuesday 10 June 2003 08:12, Ben Burton wrote:
> Sure, it was always going to come from one source package. It's the 37
> *binary* packages I was worried about, which is what the end users have
> to deal with.
Are there any thoughts or visions on how to deal with the ever-growing number
of pac
Following on from this, what about:
KDE already groups languages (well kpersonalizer does ;)) as Eastern Europe,
Western Europe, Asia, etc... Couldn't we compromise and have language packs
similarly? ie I want Chinese, so I have to put up with koffice-i18n-asia,
french koffice-i18n-weu (western
> The question is how to actually package it. All of the available options have
> clear drawbacks.
The > options as I see it are as follows.
>
> 1) Build a single koffice-i18n binary package.
> 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n).
I would make a compromise from
Le Lundi 9 Juin 2003 03:46, Ben Burton a écrit :
>
> 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n).
I think it is the best short-term solution. The only long term solution would
be to adapt the Debian packaging system for internationalization. Packager
would create one
On Dienstag, 10. Juni 2003 08:12, Ben Burton wrote:
> > 2). I've build the koffice-i18n packages in the same way that the
> > kde-i18n packages are. That avoids 37 source packages at least but only
> > gives you the languages.
>
> Sure, it was always going to come from one source package. It's the
> 2). I've build the koffice-i18n packages in the same way that the kde-i18n
> packages are. That avoids 37 source packages at least but only gives you the
> languages.
Sure, it was always going to come from one source package. It's the 37
*binary* packages I was worried about, which is what t
On Montag, 9. Juni 2003 03:46, Ben Burton wrote:
> Hi. I'd love some input here on the packaging of very large i18n
> components of software. The specific case at hand is koffice, which
> still doesn't ship with i18n files. I'd love to get this sorted out.
>
> The problem is that there is a *lot
On Mon, Jun 09, 2003 at 08:39:11PM +0200, Mathieu Roy <[EMAIL PROTECTED]> was
heard to say:
> Nikolaus Rath <[EMAIL PROTECTED]> a tapoté :
>
> > Ben Burton <[EMAIL PROTECTED]> wrote:
> > > 2) Build 37 different koffice-i18n-lang binary packages (like kde-i18n).
> > >
> > > This is bad because we
Nikolaus Rath <[EMAIL PROTECTED]> a tapoté :
> Ben Burton <[EMAIL PROTECTED]> 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 i
Ben Burton <[EMAIL PROTECTED]> 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 pr
> So, if you put all kde translations in kde-i18n-**, you will have to do this
> with the others kde apps which have a different release cycle.
FWIW, I was proposing this just for koffice (which has an unusually large
amount of i18n data), not for all KDE apps.
Ben.
Le Lundi 9 Juin 2003 15:25, Ben Burton a écrit :
> Ah, okay, I wasn't entirely clear on the kde-i18n-lang option. What I
> meant by this is that kde-i18n-lang would be updated for both KDE and
> KOffice releases, and would include code taken from both branches as
> appropriate. e.g., when KOffice
On Monday 09 June 2003 03:46, Ben Burton 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 archiv
Ah, okay, I wasn't entirely clear on the kde-i18n-lang option. What I
meant by this is that kde-i18n-lang would be updated for both KDE and
KOffice releases, and would include code taken from both branches as
appropriate. e.g., when KOffice 1.3 is released, even though KDE 3.1.2
stays the same,
On Monday 09 June 2003 05:52, John Gay 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 th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Lunes 9 de Junio de 2003 14:38, escribiste:
> Hi. :)
>
> > we already discussed this sometime ago
>
> Though not with any resolution.
>
> > and since then there are koffice-i18n-xx packages
>
> Not on the debian servers.
>
> > apt-cache show ko
Hi. :)
> we already discussed this sometime ago
Though not with any resolution.
> and since then there are koffice-i18n-xx packages
Not on the debian servers.
> apt-cache show koffice-i18n-es
> Package: koffice-i18n-es
...
> Maintainer: Ralf Nolden <[EMAIL PROTECTED]>
...
> Version: 1.2.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Lunes 9 de Junio de 2003 03:46, Ben Burton escribió:
> Hi. I'd love some input here on the packaging of very large i18n
> components of software. The specific case at hand is koffice, which
> still doesn't ship with i18n files. I'd love to get th
On Mon, Jun 09, 2003 at 04:52 +0100, John Gay wrote:
> the spanish group
> could include the different variations like brazilian, mexican etc.
That was a bad example.
Brazilians speak portuguese (wich is _not_ a spanish variation) and
mexicans speak spanish.
Kind regards,
Aníbal
pgpE1ZVwdyS5u
>Hi. I'd love some input here on the packaging of very large i18n
>components of software. The specific case at hand is koffice, which
>still doesn't ship with i18n files. I'd love to get this sorted out.
>
I remember seeing this before, but I'll add my two cents again (-;
>The problem is that
Hi. I'd love some input here on the packaging of very large i18n
components of software. The specific case at hand is koffice, which
still doesn't ship with i18n files. I'd love to get this sorted out.
The problem is that there is a *lot* of i18n material provided with
koffice. There are tran
24 matches
Mail list logo
