Bug#409782: German manual page of aptitude is incomplete
Package: aptitude Version: 0.4.4-1 I am dealing with how to remove automatically installed packages completely. Doing this, I noticed that the following options are not listed on the German manual page of aptitude: -h, --help --purge-unused --schedule-only -q[=], --quiet[=] Thanks in advance for the adjustment of the German Manpage. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409782: German manual page of aptitude is incomplete
(Finnish and Czech translators, please read on...this really concerns you as well) Quoting Simon Bienlein ([EMAIL PROTECTED]): > Package: aptitude > Version: 0.4.4-1 > > I am dealing with how to remove automatically installed packages > completely. Doing this, I noticed that the following options are not > listed on the German manual page of aptitude: > > -h, --help > --purge-unused > --schedule-only > -q[=], --quiet[=] "unfortunately", the german manpage is currently handled as a manual XML translation of the original XML file, which doesn't scale very well when changes are done to the original manpage. I'm hereby CC'ing Sebastian Kapfer who is, I think, the translator of aptitude doc files, as well as the German l10n mailing list. What could be done is switching the aptitude documentation translation to gettext, just like it has been done for French and Japanese. That would mean that a big PO file (1379 strings) would be produced from the current XML file, with all strings "fuzzy" as everyhting has to be reviewed at least once. This is a big work but a big investment in the future as the doc translation then becomes maintainable, while it isn't currently. The same goes for Finnish translation by Kaako Kangasharju (CC'ed) and the Czech translation by an unknown author. The French specialists of po4a are ready to help with that work (except translation...:-). Please just mention if you're OK. That would mean that, in the meantime, the doc (man page and all other docs) is untranslated but maybe better nothing than an outdated translation signature.asc Description: Digital signature
Bug#409782: German manual page of aptitude is incomplete
Hello, On Mon, Feb 05, 2007 at 06:09:09PM +0100, Christian Perrier wrote: > That would mean that a big PO file (1379 strings) would be produced > from the current XML file, with all strings "fuzzy" as everyhting has > to be reviewed at least once. I am strongly in favor doing this for as many man pages as possible. But this is definitly post Etch! > The French specialists of po4a are ready to help with that work > (except translation...:-). I extend my thanks for their help here. > Please just mention if you're OK. That would mean that, in the > meantime, the doc (man page and all other docs) is untranslated but > maybe better nothing than an outdated translation (Please note, I am not the one reviewing this!) This is very good post-Etch, i.e. for Lenny. For Etch, the (slightly) outdated but translated version should be kept. By experience I know that *many* translated man pages are outdated, but often they are "close enough" for most users, so by far better than a completely untranslated version. If you want, we (the german translator) can provide you with a note that some changes are not included in the translated version and hence if in doubt the english original should be used. This text of course will go, once the transition to gettext has happened, of course. Thanks for noticing and taking care of the translation! Greetings Helge -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#409782: German manual page of aptitude is incomplete
Am Montag, den 05.02.2007, 18:09 +0100 schrieb Christian Perrier: > I'm hereby CC'ing Sebastian Kapfer who is, I think, the translator of > aptitude doc files, as well as the German l10n mailing list. > > What could be done is switching the aptitude documentation translation > to gettext, just like it has been done for French and Japanese. Hello guys, I've not done any work on translating Aptitude in a while, and somebody else has been handling the main .po file for quite some time. However if "somebody" is willing to sort out the technical details (i.e. producing the .po and Makefiles and stuff), I'm willing to review/update the German translation. I agree that the XML file is a really big kludge :-) -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#409782: German manual page of aptitude is incomplete
On Mon, Feb 05, 2007 at 06:09:09PM +0100, Christian Perrier wrote: > > "unfortunately", the german manpage is currently handled as a manual > XML translation of the original XML file, which doesn't scale very > well when changes are done to the original manpage. It depends how skilled you are with basic unix tools like diff. > This is a big work but a big investment in the future as the doc > translation then becomes maintainable, while it isn't currently. I like the current way of working with xml. It gives me much more freedom over .po. * I do not need to follow the original structure so closely * I can add footnotes or whole paragraphs specific for our language * It is easier to locate the context * ...and more >From my point of view .po is good for short strings (computer UI) or reasonably small documents (short manpages). Something as big as manual for Aptitude deserves more freedom. Therefore I refuse to switch to .po for Czech translation. > The same goes for Finnish translation by Kaako Kangasharju (CC'ed) and > the Czech translation by an unknown author. You did not read credits, did you? :-) -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409782: German manual page of aptitude is incomplete
Hello, On Fri, Feb 09, 2007 at 08:18:38AM +0100, Miroslav Kure wrote: > On Mon, Feb 05, 2007 at 06:09:09PM +0100, Christian Perrier wrote: > > > > "unfortunately", the german manpage is currently handled as a manual > > XML translation of the original XML file, which doesn't scale very > > well when changes are done to the original manpage. > > It depends how skilled you are with basic unix tools like diff. Well, I don't know how aptitudes man page is handled, so this might not be the case here, but the po format has also a distinctive advantage: You get to know that a change happend (because *fuzzy* message appear, which can easily be spotted by programms which send you e-mail, write it on a web page etc.). I cannot remember having ever received a note about a changed translated man page (without po). And I simply don't have the time to locate each and every revision control system (if any) and check for changes (which might have happend upstream, or in Debian, or in a separate patch applied by Debian ...). For po files you can find lots of web pages giving you the stats, for man pages you can find lots of bug reports (like this one) by users complaining that they are outdated. > I like the current way of working with xml. It gives me much more > freedom over .po. > * I do not need to follow the original structure so closely Yes, this is a major drawback, because especially around examples the english version cannot be nicley translated into German also (e.g. the english version manages to put the entire description *before* the next paragraph with an example, while in German some words would have to go *after* the example as well, which is impossible since there is no paragraph there ...) > * I can add footnotes or whole paragraphs specific for our language I only know very few examples where language specific content should be added, and sometimes (e.g. for charsets) this would be good for upstream as well, but yes, there are (some) cases. > * It is easier to locate the context The po file is typically chronologically sorted, and you can easily "build" the man pages in a second (x)term for preview/review. But as far as I understood, this switch is an option, not mandatory. Greetings Helge -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#409782: German manual page of aptitude is incomplete
Hi, somebody in orkut named miroslav, of course not you wrote bad words on India On 2/9/07, Helge Kreutzmann <[EMAIL PROTECTED]> wrote: Hello, On Fri, Feb 09, 2007 at 08:18:38AM +0100, Miroslav Kure wrote: > On Mon, Feb 05, 2007 at 06:09:09PM +0100, Christian Perrier wrote: > > > > "unfortunately", the german manpage is currently handled as a manual > > XML translation of the original XML file, which doesn't scale very > > well when changes are done to the original manpage. > > It depends how skilled you are with basic unix tools like diff. Well, I don't know how aptitudes man page is handled, so this might not be the case here, but the po format has also a distinctive advantage: You get to know that a change happend (because *fuzzy* message appear, which can easily be spotted by programms which send you e-mail, write it on a web page etc.). I cannot remember having ever received a note about a changed translated man page (without po). And I simply don't have the time to locate each and every revision control system (if any) and check for changes (which might have happend upstream, or in Debian, or in a separate patch applied by Debian ...). For po files you can find lots of web pages giving you the stats, for man pages you can find lots of bug reports (like this one) by users complaining that they are outdated. > I like the current way of working with xml. It gives me much more > freedom over .po. > * I do not need to follow the original structure so closely Yes, this is a major drawback, because especially around examples the english version cannot be nicley translated into German also (e.g. the english version manages to put the entire description *before* the next paragraph with an example, while in German some words would have to go *after* the example as well, which is impossible since there is no paragraph there ...) > * I can add footnotes or whole paragraphs specific for our language I only know very few examples where language specific content should be added, and sometimes (e.g. for charsets) this would be good for upstream as well, but yes, there are (some) cases. > * It is easier to locate the context The po file is typically chronologically sorted, and you can easily "build" the man pages in a second (x)term for preview/review. But as far as I understood, this switch is an option, not mandatory. Greetings Helge -- Dr. Helge Kreutzmann [EMAIL PROTECTED] Dipl.-Phys. http://www.helgefjell.de 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFzJcaRsxcY/MYpWoRAqpOAKCjjrRskWkAOz+dfsTKDohcLdhvPACfamQt S4ehulOWQAgyu2xutWGe8zo= =5/y6 -END PGP SIGNATURE-
