------=_Part_96760_9372359.1171272765098
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
somebody in orkut named miroslav, of course not you wrote bad words on
India
On 2/9/07, Helge Kreutzmann <helge@[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 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
> --
> 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/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFFzJcaRsxcY/MYpWoRAqpOAKCjjrRskWkAOz+dfsTKDohcLdhvPACfamQt
> S4ehulOWQAgyu2xutWGe8zo=
> =5/y6
> -----END PGP SIGNATURE-----
>
>
------=_Part_96760_9372359.1171272765098
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div>Hi,</div>
<div> somebody in orkut named miroslav, of course
not you wrote bad words on India<br><br> </div>
<div><span class="gmail_quote">On 2/9/07, <b
class="gmail_sendername">Helge Kreutzmann</b> <<a
href="mailto:helge@[EMAIL PROTECTED]
">helge@[EMAIL PROTECTED]
>>
wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px
0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br>On Fri, Feb 09, 2007 at
08:18:38AM +0100, Miroslav Kure wrote:<br>> On Mon, Feb 05, 2007 at
06:09:09PM +0100, Christian Perrier wrote:
<br>> ><br>> > "unfortunately", the german manpage
is currently handled as a manual<br>> > XML translation of the
original XML file, which doesn't scale very<br>> > well when
changes are done to the original manpage.
<br>><br>> It depends how skilled you are with basic unix tools like
diff.<br><br>Well, I don't know how aptitudes man page is handled, so
this might<br>not be the case here, but the po format has also a
distinctive advantage:
<br><br> You get to know that a change happend (because *fuzzy*
message<br> appear, which can easily be spotted by programms
which send you<br> e-mail, write it on a web page etc.). I
cannot remember having ever<br> received a note about a changed
translated man page (without po).
<br> And I simply don't have the time to locate each and
every revision<br> control system (if any) and check for
changes (which might have<br> happend upstream, or in Debian,
or in a separate patch applied by<br> Debian ...). For po files
you can find lots of web pages giving you
<br> the stats, for man pages you can find lots of bug re****ts
(like<br> this one) by users complaining that they are
outdated.<br><br><br>> I like the current way of working with xml. It
gives me much more<br>> freedom over .po.
<br>> * I do not need to follow the original structure so
closely<br><br>Yes, this is a major drawback, because especially around
examples the<br>english version cannot be nicley translated into German
also (e.g. the<br>
english version manages to put the entire description *before* the<br>next
paragraph with an example, while in German some words would have<br>to go
*after* the example as well, which is impossible since there is<br>no
paragraph there ...)
<br><br>> * I can add footnotes or whole paragraphs specific
for our language<br><br>I only know very few examples where language
specific content should<br>be added, and sometimes (e.g. for charsets)
this would be good for
<br>upstream as well, but yes, there are (some)
cases.<br><br>> * It is easier to locate the
context<br><br>The po file is typically chronologically sorted, and you
can easily<br>"build" the man pages in a second (x)term for
preview/review.
<br><br>But as far as I understood, this switch is an option, not
mandatory.<br><br>Greetings<br><br> Helge<br>--<br>
Dr. Helge
Kreutzmann <a
href="mailto:helge@[EMAIL PROTECTED]
">helge@[EMAIL PROTECTED]
><br>
Dipl.-Phys.
<a
href="http://www.helgefjell.de">http://www.helgefjell.de</a><br>
64bit GNU
powered
gpg signed mail
preferred<br> Help
keep free software "libre":
<a href="http://www.ffii.de/">http://www.ffii.de/</a><br><br>-----BEGIN
PGP SIGNATURE-----<br>Version: GnuPG v1.4.1
(GNU/Linux)<br><br>iD8DBQFFzJcaRsxcY/MYpWoRAqpOAKCjjrRskWkAOz+dfsTKDohcLdhvPACfamQt<br>S4ehulOWQAgyu2xutWGe8zo=
<br>=5/y6<br>-----END PGP SIGNATURE-----<br><br></blockquote></div><br>
------=_Part_96760_9372359.1171272765098--
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@[EMAIL PROTECTED]
a subject of "unsubscribe". Trouble? Contact
listmaster@[EMAIL PROTECTED]
|
