-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
> I would like to propose a change to the KOffice packagers to include an
> independent i18n package for KOffice.
Indeed, doing koffice i18n properly has been on my TODO list for a long time
now; it's highly non-trivial though which is why I haven't done it to date.
I suspect I need to bump it up to a higher priority. :)
The fact that koffice and kde are on independent release schedules does make a
strong argument for separating koffice-i18n from kde-i18n. It's not clear
though how a separate koffice-i18n should be done; one massive koffice-i18n
(an inconveniently large package) or many small koffice-i18n-xx packages (yet
more package bloat)? There are strong arguments for each, as well as
arguments for keeping koffice stuff in the kde-i18n-xx packages regardless of
the release schedule.
Hmm.. I'll think on it some more; suggestions are of course welcome (mailed to
debian-kde would be great).
Ben.
- --
Ben Burton
[EMAIL PROTECTED] | [EMAIL PROTECTED]
Public Key: finger [EMAIL PROTECTED]
Yeah the world's falling apart, but it's doing it gently and with class.
- Geoff Bowmer on the record low Australian dollar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9hcwzMQNuxza4YcERAntCAJ0e/F+b+H22ZIc/0gX1TgDpfmlmGACffJvL
PNbxEusfDGiYpdiVs3E3mBs=
=cUqK
-----END PGP SIGNATURE-----
