[parted-devel] [PATCH] Bump library REVISION number for release

[Mario Blättermann]

Hi Brian and all,

Am 17.07.2014 17:07, schrieb Brian C. Lane:
> On Thu, Jul 17, 2014 at 10:38:33AM -0400, Phillip Susi wrote:
>> On 7/17/2014 12:51 AM, Mario Blättermann wrote:
>>> I still have an objection. For some months, I try to get my German
>>> man page translations included, but in fact nothing happened. An
>>> appropriate po4a infrastructure already exists, and Brazilian
>>> Portuguese translations are present. Obviously nobody cares about
>>> man page translations, are there good reasons for...? If not,
>>> please add my already submitted files to the Git repo so that they
>>> get included in the upcoming release.
>>
>> I thought that infrastructure was broken and didn't build the man
>> page?  Unfortunately I am not familiar enough enough with
>> internationalization to fix it.
> 
> I don't think this should block the release, but we should sort it out
> for the next one.
> 
Hopefully you mean a *reasonable* time frame... The latest stable release was
more than two years ago. Would be not that nice to wait two years again.

The already existing Brazilian Portuguese translations are there for years
(appeared first in 2006). Wouldn't it be the time now to get them really
released? Maybe we need another approach for implementing po4a. No special i18n
skills are required, we need only someone with valuable Autotools knowledge.

Have a look at the attached scripts: create-docs-pot.sh creates the templates
for man pages and texinfo manual. Due to the differences between the source
formats, they should be kept apart from each other. The script assumes existing
"man" and "texi" directories so far. Finally translate-docs.sh generates the
native language versions in the appropriate directory structure for
installation. Note, currently we don't have a guideline where to install
translated texinfo stuff. For the time being we can use the language-specific
suffix for installation, but the more important thing is to get some native
language files for publishing on the web (html, dvi, pdf etc. need to be
included in gendocs.sh).

GNU Autotools is an almost blank area for me, maybe someone can help out with
integrating my scripts into the release/installation workflow? I've already
tried to get familiar with the way recommended by the po4a developers (po4a.mk
and po4a.conf) but it seems too difficult and covers odd cases which we don't
need, such as non-UTF8 files and extra injection of translator acknowledgements.

However, good luck with the final 3.2 release if you don't consider the broken
po4a implementation as a blocker, but anyway, would be nice to see the
translated docs soon in a release, in view of the age of the pt_BR translations.
And believe me, once the templates are available from TP, new contributors will
arrive. I'm quite sure the Ukrainian translator Yuri Chornoivan will be the
first one, he's very interested in doc translations.

Best Regards,
Mario
-------------- next part --------------
A non-text attachment was scrubbed...
Name: create-docs-pot.sh
Type: application/x-shellscript
Size: 561 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/parted-devel/attachments/20140717/e9812233/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: translate-docs.sh
Type: application/x-shellscript
Size: 1220 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/parted-devel/attachments/20140717/e9812233/attachment-0001.bin>