This is a MIME-formatted message. If you see this text it means that your
E-mail software does not sup****t MIME-formatted messages.
--=_ipx22193-8018-1171035930-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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:
> >=20
> > "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.
>=20
> 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 re****ts (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
--=20
Dr. Helge Kreutzmann helge@[EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
--=_ipx22193-8018-1171035930-0001-2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Transfer-Encoding: 7bit
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFzJcaRsxcY/MYpWoRAqpOAKCjjrRskWkAOz+dfsTKDohcLdhvPACfamQt
S4ehulOWQAgyu2xutWGe8zo=
=5/y6
-----END PGP SIGNATURE-----
--=_ipx22193-8018-1171035930-0001-2--
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@[EMAIL PROTECTED]
a subject of "unsubscribe". Trouble? Contact
listmaster@[EMAIL PROTECTED]
|
