Bug#438676: hex-a-hop: Switch to po4a for man page translation

[Helge Kreutzmann]

Hello Jens,
On Thu, Aug 23, 2007 at 03:41:02AM +0200, Jens Seidel wrote:
> first of all sorry for ignoring your patch so long.

> On Sat, Aug 18, 2007 at 11:24:04PM +0200, Helge Kreutzmann wrote:

Well, "5 days" is not "so long" (I've bug report being ignored (even
with patch) for over one year!)

> > 1. Add the following line in your debian/rules, where X1, X2, X3, ..
> >    are all languages you've received man page translations for:
> >    po4a-updatepo -f man -m hex-a-hop.6 -p hex-a-hop.X1.po -p hex-a-hop.X2.po -p
> > hex-a-hop.X3.po
> >    This call will synchronise the various .po files with the original
> >    (there is no .pot file involved!).
> 
> I do not like the fact that still another PO/POT file is involved.
> Wouldn't it be easier for translators to have only one PO/POT file? This
> way it is also possible to reuse common translations and to check for
> consistency in the program and manual page.

Fine with me, but as I am not a debconf wizard, I am afraid, I can't
help you with this non-standard use case. So far, man pages have been
dealt differently than debconf or program messages.

> Could it be that it is impossible to handle this with one POT file?
> Shouln't we file a few wishlist bugs against po4a, gettext, ...?

I don't know, feel free to submit a wishlist bug.

> > 3. For each language you've received translations for, add the
> >    following line in your debian/rules:
> >    po4a-translate -f man -m hex-a-hop.6 -p hex-a-hop.Xi.po -a hex-a-hop.Xi.add -l hex-a-hop.Xi.6
> 
> This should work even if hex-a-hop.Xi.po contains more messages
> (includes the master PO file), right?

Yes, this should work even then. 

> > 4. Add the following note where other people can find it, e.g.
> >    README.Debian:
> > 
> >    Note to translators:
> 
> Do you really think this belongs to README.Debian? It is an internal
> detail (we also do not install the POT file in binaries -- only in
> source). If we use only a single PO file we do not need to explain
> anything, right?

Please note I said "e.g.". And yes, a single PO file would suffice,
though I still suggest adding a note that a man page is involved as
well.

> > 6. Once you received hex-a-hop.vi.po, hex-a-hop.de.po,
> >    hex-a-hop.de.add and possibly hex-a-hop.vi.add, copy them to
> >    debian/.
> 
> Hey, what about Russian, Bulgarian, Dutch and Spanish :-?

No prejudice against any langauge, I just used an example at the time
this transition was made (and especially the vi translator requested
this change on a public maling list).

Greetings

             Helge

-- 
      Dr. Helge Kreutzmann                     debian at helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-games-devel/attachments/20070823/cc02b812/attachment.pgp