A suggestion: i18n for KOffice
Hello, I would like to propose a change to the KOffice packagers to include an independent i18n package for KOffice. At the moment translations for the different languages are provided in kde-i18n-xx packages, according to the main KDE releases. However KDE releases are not in sync with KOffice releases, because they are independent. This leads to having the latest KOffice packages for the latest stable branch but not its corresponding updated translations. I can show this with an example; now Ben Burton has released KOffice 1.2, but the translations for this version are in the HEAD branch and are tagged as KOFFICE_1_2_RELEASE. However the KOffice 1.2 packages are built for KDE 3.0.3, which I think is __totally__ correct. On the other hand the translations applied to KOffice come from the KDE_3_0_BRANCH, so that some applications appear partially translated and others not translated at all, while the translations are completed in the CVS. I propose a solution for this, but I am sorry because it means more work for the KOffice packager (Ben Burton in this case), it would be to release koffice-i18n-xx packages, which would be created extracting from the CVS all messages and documents tagged as KOFFICE_X_Y_RELEASE. And to prevent that the files with messages and documentation are not overwritten by the kde-i18n-xx packages, the koffice part of this package should be removed from the kde-i18n-xx packages. regards, and many thanks to all Debian packagers for KDE for their work. Pablo de Vicente KDE-es translation team.
Re: A suggestion: i18n for KOffice
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 11:13 am, Pablo de Vicente wrote: Hello, I would like to propose a change to the KOffice packagers to include an independent i18n package for KOffice. At the moment translations for the different languages are provided in kde-i18n-xx packages, according to the main KDE releases. However KDE releases are not in sync with KOffice releases, because they are independent. This leads to having the latest KOffice packages for the latest stable branch but not its corresponding updated translations. I can show this with an example; now Ben Burton has released KOffice 1.2, but the translations for this version are in the HEAD branch and are tagged as KOFFICE_1_2_RELEASE. However the KOffice 1.2 packages are built for KDE 3.0.3, which I think is __totally__ correct. On the other hand the translations applied to KOffice come from the KDE_3_0_BRANCH, so that some applications appear partially translated and others not translated at all, while the translations are completed in the CVS. I propose a solution for this, but I am sorry because it means more work for the KOffice packager (Ben Burton in this case), it would be to release koffice-i18n-xx packages, which would be created extracting from the CVS all messages and documents tagged as KOFFICE_X_Y_RELEASE. And to prevent that the files with messages and documentation are not overwritten by the kde-i18n-xx packages, the koffice part of this package should be removed from the kde-i18n-xx packages. regards, and many thanks to all Debian packagers for KDE for their work. Pablo de Vicente KDE-es translation team. This is really an upstream problem. They probably should not have seperate releases for koffice and KDE, but have all the translations in one place maybe you could suggest that they split up the koffice and kde translations. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9hcbVYsCKa6wDNXYRAskGAJib8No9ojOuOWk/WYusEW5cCoYMAJ9G14jU N/iDtbmTfZNwN8ZB0VajzA== =nCbI -END PGP SIGNATURE-
Re: A suggestion: i18n for KOffice
-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-
Re: A suggestion: i18n for KOffice
Le Lundi 16 Septembre 2002 14:18, Ben Burton a écrit : 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 i'am in favor of small packages for koffice. I can help for that i it is needed. -- Opensides sprl Benoit Mortier - Linux Engineer
