Debian Installer Manual Translations (was: repository branched for sarge)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (please keep both d-boot and d-i18n CC'ed for this discussion) On Tuesday 30 November 2004 06:52, Christian Perrier wrote: In my opinion, that counts first for changes to the original version of the manual. However, as soon as some English is changed in the manual, there's of course no permission to request for updating translations. Frans, do you agree with that interpretation? To be honest I'm not sure how the manual should be maintained after the branching. Maybe we should discuss our options; I'll give a start below. Comments very welcome. For the English original I feel that for the time being most changes in trunk could safely go to the Sarge branch: there are plenty of improvements possible that are relevant for Sarge, including the planned reorganization of Chapter 2 (which I plan to start this weekend). I would not like to discourage changes relevant for Sarge by focussing on post-Sarge too soon and IMHO maintaining two versions is way to complicated and too much work (which would discourage work on the manual even more). The only changes to the manual that should not go into the Sarge branch would be those relating to post-sarge development, like localechooser. I would suggest we postpone making these changes for the time being In some cases, we could even consider documenting both the old and new way d-i works by adding notes. Translations that have been officially included (es, fr, ja, pt_BR, sp) === For these any changes made in the Sarge branch in the English docs should preferably be translated as well. If translations are out-of-date (like pt_BR currently), I guess it would be good update these in both branches. All other translations == These are only shown on the d-i manual website. As these translations are build from trunk, I see no advantage in updating these translations in the Sarge branch, as there would be risks in including extra translations on the CD's in later builds. In fact, it would probably be safer to delete these languages in the Sarge branch. At some future time, when d-i really starts to diverge from it's Sarge version, this proposed policy should of course be reconsidered. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBrd8Vgm/Kwh6ICoQRAsmvAKDS9EthIFmJmlGGY2RIocv9x3h2/wCfYcIB dj9C3l/HIDBaeaq/RU1EARU= =p9gG -END PGP SIGNATURE-
Re: Debian Installer Manual Translations (was: repository branched for sarge)
Hi, All other translations == These are only shown on the d-i manual website. As these translations are build from trunk, I see no advantage in updating these translations in the Sarge branch, as there would be risks in including extra translations on the CD's in later builds. In fact, it would probably be safer to delete these languages in the Sarge branch. So it isn't possible to get a german version on the CD anymore? :-( Greetings Holger -- == Created with Sylpheed-Claws 0.9.12 under Debian GNU LINUX 3.1 Sarge (testing). http://counter.li.org/ Registered LinuxUser #311290 Spamfiltering powered by www.spamassassin.org = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer Manual Translations (was: repository branched for sarge)
For the English original I feel that for the time being most changes in trunk could safely go to the Sarge branch: there are plenty of improvements possible that are relevant for Sarge, including the planned reorganization of Chapter 2 (which I plan to start this weekend). I would not like to discourage changes relevant for Sarge by focussing on post-Sarge too soon and IMHO maintaining two versions is way to complicated and too much work (which would discourage work on the manual even more). The only changes to the manual that should not go into the Sarge branch would be those relating to post-sarge development, like localechooser. I fully agree with that view (and *not* only because this allows me to avoid writing documentation for localechooser). There is no urgent need for updates relevant to new material as we will probably be still focused on the sarge version for some time after the release of no-name-yet. All other translations == These are only shown on the d-i manual website. As these translations are build from trunk, I see no advantage in updating these translations in the Sarge branch, as there would be risks in including extra translations on the CD's in later builds. In fact, it would probably be safer to delete these languages in the Sarge branch. Supported as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer Manual Translations (was: repository branched for sarge)
On Wed, Dec 01, 2004 at 04:11:07PM +0100, Frans Pop wrote: Translations that have been officially included (es, fr, ja, pt_BR, sp) sp? === For these any changes made in the Sarge branch in the English docs should preferably be translated as well. If translations are out-of-date (like pt_BR currently), I guess it would be good update these in both branches. All other translations == These are only shown on the d-i manual website. As these translations are build from trunk, I see no advantage in updating these translations in the Sarge branch, as there would be risks in including extra translations on the CD's in later builds. In fact, it would probably be safer to delete these languages in the Sarge branch. But the install manual used on the official Debian website will surely be built from the sarge branch when the time comes; even if these languages don't make it onto the CDs, we'd just have to add them back to the sarge branch later for the website maintenance, no? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
