Re: [Libexif-devel] Translations for the exif.1 man page

[Mario B. <mar...@gm...>]

Hi all,

Am 03.04.2014 10:52, schrieb Mario Blättermann:
> Hi Dan,
> 
> Am 03.04.2014 09:02, schrieb Dan Fandrich:
>> On Tue, Mar 18, 2014 at 01:36:57PM +0100, Mario Blättermann wrote:
>>> both the libexif library and the exif command line tool are translatable
>>> at translationproject.org. But we should also internationalize the exif man
>>> page and publish the translation template there.
>>>
>>> Using po4a this is quite easy. Have a look at the attachment. There you'll
>>> find two scripts which generate the pot file and translate the po files
>>> back to the actual man page, respectively. For testing purposes, I've also
>>> added a German translation file.
>>
>> I've never seen manual pages translated using the .po mechanism like this.
> 
> Most of the (active) external translation projects like man-pages-de or
> man-pages-fr already use po4a. Moreover, the Debian folks uses it for almost all
> the dpkg and apt man pages.
> 
>> It makes good sense as the translation workflow is unaltered.
>>
> 
> The translation workflow...? I assume you mean the workflow on translators side.
> That's unaltered. Translators get a pot template from the TP robot, translate
> the messages and send it back. That's the greatest advantage of po4a: Nobody has
> to bother with plain text, which would include to figure out a way to track
> upstream changes accordingly. In other words, I wouldn't start on a translation
> without po files.
> 
>>> We need some glue code to install the files accordingly, but I don't know 
>>> anything about how the Autotools work, sorry. The translated files itself
>>> are already in the correct paths when using the scripts ($PREFIX/man still
>>> has to be preceded).
>>>
>>> In general, the generation of the translated man pages should happen before
>>> the release tarball will be created. That way packagers don't have to
>>> bother with po4a, especially if a po4a package is missing from certain
>>> distributions. Shouldn't be a problem, the man pages are arch-independent
>>> anyway.
>>>
>>> Besides that, the localized versions could be presented at the website,
>>> too. The English one is already present.
>>
>> I'll take a look at what it would take to integrate this. Thanks for
>> bringing it to our attention.
>>
> Thanks for your interest.
> 
Any news about that? Do you need some more info? Unfortunately, I cannot help
out with implementing this, besides to use my scripts. Even if it doesn't work
yet in the build chain, the module on TP could be created to get man pages in
more native languages. This gives translators some extra time to work on this.

Best Regards,
Mario