3:02 p.m.
Greetings po4a people.
My name is Daniel Cabrera, and I'm one of the members of the Fedora
Spanish translation team. We've decided to start updating our man pages,
and for that, we've found that po4a is the perfect tool. Since we are
very few in our team, and since we're more accustomed to use graphical
programs, I'm having a couple of troubles that maybe you could help me
solve.
Our working plan is to first convert all of our outdated database (v.
1.55) into .po files, and then update them to 3.25... if that's the last
version. So, my first problem is that when I try to convert a man page
into a .po file, the translated strings are placed as msgid strings. I'm
using as a source file a man page already in Spanish (accept.2, for this
example), and the command I'm running is:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2-es-ES.po
My second problem is to be able to convert more than a file at once, but
that can wait :-)
Thanks a lot for your time
Regards, Daniel.
3:45 p.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On 2010/9/20 daniel cabrera:
Greetings po4a people.
My name is Daniel Cabrera, and I'm one of the members of the Fedora
Spanish translation team. We've decided to start updating our man pages,
and for that, we've found that po4a is the perfect tool. Since we are
very few in our team, and since we're more accustomed to use graphical
programs, I'm having a couple of troubles that maybe you could help me
solve.
Our working plan is to first convert all of our outdated database (v.
1.55) into .po files, and then update them to 3.25... if that's the last
version. So, my first problem is that when I try to convert a man page
into a .po file, the translated strings are placed as msgid strings. I'm
using as a source file a man page already in Spanish (accept.2, for this
example), and the command I'm running is:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2-es-ES.po
Hi Daniel,
(I do not know whether you subscribed, thus Cc: you)
In order to produce meaningful PO files, you have to run
po4a-gettextize with an English file and its translation. I
downloaded man-pages-es 1.55 from
http://www.ditec.um.es/~piernas/manpages-es/.
I did not find man-pages 1.55 (do you have a copy?), but found 1.56 here:
http://rpmfind.net//linux/RPM/PLD/dists/ra/updates/general/SRPMS/man-page...
After extracting those tarballs, my directory contains:
man-pages-1.56 man-pages-es-1.55
Then
$ po4a-gettextize -f man -m man-pages-1.56/man2/accept.2 \
-l man-pages-es-1.55/man2/accept.2 -L UTF-8 -p accept.2-es-ES.po
works just fine. Some English manual pages contain accented letters,
you will then have to specify its encoding with the -M flag.
One more point: some manual pages have been removed (for instance most
pages under section 1), do not lose time converting them to PO files.
(But beware that some pages have been moved into another section)
My second problem is to be able to convert more than a file at once,
but
that can wait :-)
Here we go: WARNING: These commands remove files after converting them
to PO files!!!
Make sure to use a VCS or work on a copy.
$ for f in man-pages-es-1.55/man*/*.?; do
echo Processing $f;
po4a-gettextize -f man \
-m man-pages-1.56${f#man-pages-es-1.55} \
-l $f -L UTF-8 -p $f.po 2>/dev/null && rm -f $f;
done
$ git ls-files --deleted | wc -l
1114
$ git ls-files man-pages-es-1.55/man? | wc -l
1303
Thus po4a-gettextize did successfully convert 1114 files from 1303.
You will have to manually check failing pages; this is pretty boring,
but you have to do that task only once.
Denis
7:39 a.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On Mon, 2010-09-20 at 22:45 +0200, Denis Barbier wrote:
Hi Daniel,
(I do not know whether you subscribed, thus Cc: you)
In order to produce meaningful PO files, you have to run
po4a-gettextize with an English file and its translation. I
downloaded man-pages-es 1.55 from
http://www.ditec.um.es/~piernas/manpages-es/.
I did not find man-pages 1.55 (do you have a copy?), but found 1.56 here:
http://rpmfind.net//linux/RPM/PLD/dists/ra/updates/general/SRPMS/man-page...
After extracting those tarballs, my directory contains:
man-pages-1.56 man-pages-es-1.55
Then
$ po4a-gettextize -f man -m man-pages-1.56/man2/accept.2 \
-l man-pages-es-1.55/man2/accept.2 -L UTF-8 -p accept.2-es-ES.po
works just fine. Some English manual pages contain accented letters,
you will then have to specify its encoding with the -M flag.
One more point: some manual pages have been removed (for instance most
pages under section 1), do not lose time converting them to PO files.
(But beware that some pages have been moved into another section)
> My second problem is to be able to convert more than a file at once, but
> that can wait :-)
Here we go: WARNING: These commands remove files after converting them
to PO files!!!
Make sure to use a VCS or work on a copy.
$ for f in man-pages-es-1.55/man*/*.?; do
echo Processing $f;
po4a-gettextize -f man \
-m man-pages-1.56${f#man-pages-es-1.55} \
-l $f -L UTF-8 -p $f.po 2>/dev/null && rm -f $f;
done
$ git ls-files --deleted | wc -l
1114
$ git ls-files man-pages-es-1.55/man? | wc -l
1303
Thus po4a-gettextize did successfully convert 1114 files from 1303.
You will have to manually check failing pages; this is pretty boring,
but you have to do that task only once.
Denis
Denis, thank you very much for your explanation. It took me on the right
track and now it's just a matter of time before we can update all those
man pages.
Best regards, Daniel.
1:42 p.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On 2010/9/21 daniel cabrera wrote:
[...]
Denis, thank you very much for your explanation. It took me on the
right
track and now it's just a matter of time before we can update all those
man pages.
Great news.
One more word, when you have converted your manual pages to PO files,
you may consider to join the perkamon project, as Simon already told
you. I am syncing PO files, you will then have to only worry about
updating your PO files, you may even use Transifex for that purpose if
you want.
Denis
3:28 p.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On Tue, 2010-09-21 at 20:42 +0200, Denis Barbier wrote:
Great news.
One more word, when you have converted your manual pages to PO files,
you may consider to join the perkamon project, as Simon already told
you. I am syncing PO files, you will then have to only worry about
updating your PO files, you may even use Transifex for that purpose if
you want.
Denis
Denis, of course I will, that's our plan. Please note that the final
decision does not depend on us (I mean, the Spanish team), but as long
as we can still use Transifex, I don't see any problems there.
(Speaking of which, I have a couple of questions about this, related to
minor issues, but I'm not sure if this is the place for asking.
May I open a new thread, or should I talk to you private?)
Best regards, daniel.
12:29 a.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On 2010/9/21 daniel cabrera wrote:
On Tue, 2010-09-21 at 20:42 +0200, Denis Barbier wrote:
>
> Great news.
> One more word, when you have converted your manual pages to PO files,
> you may consider to join the perkamon project, as Simon already told
> you. I am syncing PO files, you will then have to only worry about
> updating your PO files, you may even use Transifex for that purpose if
> you want.
>
> Denis
Denis, of course I will, that's our plan. Please note that the final
decision does not depend on us (I mean, the Spanish team), but as long
as we can still use Transifex, I don't see any problems there.
(Speaking of which, I have a couple of questions about this, related to
minor issues, but I'm not sure if this is the place for asking.
May I open a new thread, or should I talk to you private?)
I usually prefer discussions on a public mailing list, but as you
know, I will reply if for some reason you prefer private discussions
;)
If your issues are related in any way to po4a, here is the right
place. Otherwise you can ask on
http://lists.alioth.debian.org/mailman/listinfo/perkamon-devel
Denis
10:28 a.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On Wed, 2010-09-22 at 07:29 +0200, Denis Barbier wrote:
I usually prefer discussions on a public mailing list, but as you
know, I will reply if for some reason you prefer private discussions
;)
If your issues are related in any way to po4a, here is the right
place. Otherwise you can ask on
http://lists.alioth.debian.org/mailman/listinfo/perkamon-devel
Denis
Ok, here is my question:
Our plan is to update our 1.55 *.es.po files, with the 3.26
*.pot files. In order to do that, I need those 3.26 *.pot files.
Accidentally, I 've found that my first (wrong) command to create a
*.es.po file:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2-es-ES.po
works like a charm if a want to create the .pot file:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2.pot
Is this OK? I mean, if I can't find the *.pot files, may I use this
command without worrying about braeking anything in the future? I looked
at it, and looked at the updated *.es.po file that I've create with it,
and they seems fine.
Daniel
11:34 a.m.
New subject: [Po4a-devel] Introduction, and a polite request for help
On 2010/9/22 daniel cabrera wrote:
On Wed, 2010-09-22 at 07:29 +0200, Denis Barbier wrote:
>
> I usually prefer discussions on a public mailing list, but as you
> know, I will reply if for some reason you prefer private discussions
> ;)
> If your issues are related in any way to po4a, here is the right
> place. Otherwise you can ask on
> http://lists.alioth.debian.org/mailman/listinfo/perkamon-devel
>
> Denis
Ok, here is my question:
Our plan is to update our 1.55 *.es.po files, with the 3.26
*.pot files. In order to do that, I need those 3.26 *.pot files.
Right.
Accidentally, I 've found that my first (wrong) command to create
a
*.es.po file:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2-es-ES.po
works like a charm if a want to create the .pot file:
$ po4a-gettextize -f man -m accept.2 -M UTF-8 -p accept.2.pot
Is this OK? I mean, if I can't find the *.pot files, may I use this
command without worrying about braeking anything in the future? I looked
at it, and looked at the updated *.es.po file that I've create with it,
and they seems fine.
You can do that, and then run msgmerge. We provide a dedicated tool,
po4a-updatepo, to scan a new master document and update existing PO
file:
$ po4a-updatepo -f man -m man-pages-3.26/man2/accept.2 -p
accept.2-es-ES.po --previous
Unfortunately the --previous argument has been broken since po4a 0.38,
I guess that this is what Russian folks have written in
https://man-pages-ru.svn.sourceforge.net/svnroot/man-pages-ru/Jamfile
Anyway one can safely replace the --previous flag by
--msgmerge-opt=--previous, it will work with any version of po4a.
We did not notice this bug earlier because we now use exclusively the
po4a command-line tool, it is much more convenient than po4a-updatepo
+ po4a-translate. I will give more details when replying to your
other post on perkamon-devel.
IIRC many manual pages have been moved between 1.55 and 3.26, so it
may be convenient to create a compendium file and run msgmerge -C:
$ msgcat *.po > compendium.es
$ po4a-updatepo -f man -m man-pages-3.26/man2/accept.2 \
-p accept.2-es-ES.po --msgmerge-opt='--previous -C compendium.es'
But you will first have to edit compendium.es and check msgstr which
have different translations:
msgstr ""
"#-#-#-#-# file1.po #-#-#-#-#\n"
"A translation\n"
"#-#-#-#-# file2.po #-#-#-#-#\n"
"Another translation"
You choose the one you want to keep and remove trailing \n.
Please note that you will have to do that only once; if you join
perkamon, I will take care of those updates myself.
Denis
5205
days inactive
5207
days old
7 comments
2 participants
participants (2)
-
daniel cabrera -
Denis Barbier