6:58 p.m.
Hello,
In a project I am translating into French, I recently discovered that
developers use
po4a-gettextize -o porefs=none ...
to generate PO files without line numbers in references. The
advantage is that POT file is not modified when line numbers change.
Of course, the drawback is that we are losing some information. For
instance, po4aman-display-po could not work on such PO files (and I
really like this tool).
The -o flag above means that porefs is an option of the
Locale::Po4a::Po module. In the last days, I made some commits to also
add a --porefs option to po4a, so that this option is available when
using po4a with a configuration file (instead of calling
po4a-gettextize, po4a-updatepo and po4a-translate).
It works great, I also just added another option --porefs=counter to
not break po4aman-display-po ;)
I will soon update PO files so that you can translate documentation
about these new options. But I want to build PO files with
--porefs=counter. The problem is that I do not know how to do that
with the current build system. So unless someone explains how to do
that with po4a-build, I will very soon revert our build system to
using plain configuration files.
Denis
12:31 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On Tue, 18 Sep 2012 01:58:51 +0200
"D. Barbier" <bouzim(a)gmail.com> wrote:
I will soon update PO files so that you can translate documentation
about these new options. But I want to build PO files with
--porefs=counter. The problem is that I do not know how to do that
with the current build system. So unless someone explains how to do
that with po4a-build, I will very soon revert our build system to
using plain configuration files.
Throwing baby out with the bath water...
po4a-build.conf IS a plain configuration file....
po4a-build isn't hard to tweak. It calls po4a itself. All that's needed
is code similar to the KEEP option in the config which sets a value and
it should probably be generic, so make it PO4AOPTIONS or similar.
Modify our po4a-build.conf to specify what is needed then put that in
each call to po4a (internal and external use) in the same was as the
KEEP option in the config generates a $K variable which is passed to
po4a.
Needs to be done for the POTONLY call as well.
Then add documentation (and get it translated) for the new option.
I'm away at the moment but there can't be any reason to rush this out
during a release freeze, so there is plenty of time to get this done
without throwing away po4a-build.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
2:29 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On 2012/9/18 Neil Williams <codehelp(a)debian.org>:
On Tue, 18 Sep 2012 01:58:51 +0200
"D. Barbier" <bouzim(a)gmail.com> wrote:
> I will soon update PO files so that you can translate documentation
> about these new options. But I want to build PO files with
> --porefs=counter. The problem is that I do not know how to do that
> with the current build system. So unless someone explains how to do
> that with po4a-build, I will very soon revert our build system to
> using plain configuration files.
Throwing baby out with the bath water...
Nothing is thrown away at the moment, I am just changing how po4a
generates its own PO files. But if nobody maintains it, yes it may
get dropped at some point.
po4a-build.conf IS a plain configuration file....
po4a-build isn't hard to tweak. It calls po4a itself. All that's needed
is code similar to the KEEP option in the config which sets a value and
it should probably be generic, so make it PO4AOPTIONS or similar.
Modify our po4a-build.conf to specify what is needed then put that in
each call to po4a (internal and external use) in the same was as the
KEEP option in the config generates a $K variable which is passed to
po4a.
Needs to be done for the POTONLY call as well.
Then add documentation (and get it translated) for the new option.
No problem. While you are at it, please also fix
http://bugs.debian.org/557665
http://bugs.debian.org/600003
I'm away at the moment but there can't be any reason to rush
this out
during a release freeze, so there is plenty of time to get this done
without throwing away po4a-build.
Funny. I cannot see any reason why po4a development should stop
during Debian release freeze.
Denis
5:04 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On Tue, 18 Sep 2012 09:29:12 +0200
"D. Barbier" <bouzim(a)gmail.com> wrote:
On 2012/9/18 Neil Williams <codehelp(a)debian.org>:
>> I will soon update PO files so that you can translate documentation
>> about these new options. But I want to build PO files with
>> --porefs=counter. The problem is that I do not know how to do that
>> with the current build system. So unless someone explains how to do
>> that with po4a-build, I will very soon revert our build system to
>> using plain configuration files.
>
> Throwing baby out with the bath water...
Nothing is thrown away at the moment, I am just changing how po4a
generates its own PO files. But if nobody maintains it, yes it may
get dropped at some point.
As I've already said, I'm away at the moment and I'll be v.busy with the
Debian release when I get back. I don't see why someone else can't make
this tweak. I also don't see any point in rushing this through to make a
po4a release any time soon.
> po4a-build.conf IS a plain configuration file....
>
> po4a-build isn't hard to tweak. It calls po4a itself. All that's needed
> is code similar to the KEEP option in the config which sets a value and
> it should probably be generic, so make it PO4AOPTIONS or similar.
> Modify our po4a-build.conf to specify what is needed then put that in
> each call to po4a (internal and external use) in the same was as the
> KEEP option in the config generates a $K variable which is passed to
> po4a.
>
> Needs to be done for the POTONLY call as well.
>
> Then add documentation (and get it translated) for the new option.
No problem. While you are at it, please also fix
http://bugs.debian.org/557665
Actually, what I've described would allow for this bug to be closed,
the same mechanism would provide for both.
> I'm away at the moment but there can't be any reason to
rush this out
> during a release freeze, so there is plenty of time to get this done
> without throwing away po4a-build.
Funny. I cannot see any reason why po4a development should stop
during Debian release freeze.
Time is finite and po4a is not my only project - Emdebian comes first,
then Debian then some other upstreams. It's not as if I'm the only
person who could do this stuff but my time is already allocated until
Wheezy is released.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
5:52 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On 2012/9/18 Neil Williams wrote:
On Tue, 18 Sep 2012 09:29:12 +0200
"D. Barbier" <bouzim(a)gmail.com> wrote:
> On 2012/9/18 Neil Williams <codehelp(a)debian.org>:
> >> I will soon update PO files so that you can translate documentation
> >> about these new options. But I want to build PO files with
> >> --porefs=counter. The problem is that I do not know how to do that
> >> with the current build system. So unless someone explains how to do
> >> that with po4a-build, I will very soon revert our build system to
> >> using plain configuration files.
> >
> > Throwing baby out with the bath water...
>
> Nothing is thrown away at the moment, I am just changing how po4a
> generates its own PO files. But if nobody maintains it, yes it may
> get dropped at some point.
As I've already said, I'm away at the moment and I'll be v.busy with the
Debian release when I get back. I don't see why someone else can't make
this tweak.
AFAICT you are the only one interested by po4a-build; I could not find
any po4a-build usage except in po4a, emdebian and svn-buildpackage.
I also don't see any point in rushing this through to make a
po4a release any time soon.
This is the other way: I want to make a po4a release, mostly because
of the new --porefs option (I may also work a bit about AsciiDoc
support). I already lost several hours when preparing previous
releases and am getting fed up, this is why I want to get back. You
had almost 3 years to add the features that were present before you
switched our build system to po4a-build (support for addenda and
general options), I do not see why I should wait any longer.
Denis
6:23 p.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On 2012/9/18 D. Barbier wrote:
[...]
I will soon update PO files so that you can translate documentation
about these new options.
[...]
Hello,
I would like to release po4a 0.43 on 17th, October, please update your
translations.
Here are current PO stats:
po/bin (pot: 28929)
af: po/bin/af.po: 22t30f150u
bn: po/bin/bn.po: 3t9f190u
ca: po/bin/ca.po: 143t14f45u
cs: po/bin/cs.po: 200t1f1u
da: po/bin/da.po: 105t97u
de: po/bin/de.po: 201t1u
eo: po/bin/eo.po: 200t1f1u
es: po/bin/es.po: 201t1u
et: po/bin/et.po: 200t1f1u
eu: po/bin/eu.po: 200t1f1u
fr: po/bin/fr.po: 200t1f1u
he: po/bin/he.po: 3t9f190u
hr: po/bin/hr.po: 29t17f156u
id: po/bin/id.po: 125t27f50u
it: po/bin/it.po: 132t22f48u
ja: po/bin/ja.po: 200t1f1u
kn: po/bin/kn.po: 29t35f138u
ko: po/bin/ko.po: 16t16f170u
ku: po/bin/ku.po: 4t8f190u
nb: po/bin/nb.po: 51t39f112u
nl: po/bin/nl.po: 20t15f167u
oc: po/bin/oc.po: 4t20f178u
pl: po/bin/pl.po: 200t1f1u
pt: po/bin/pt.po: 185t1f16u
pt_BR: po/bin/pt_BR.po: 36t37f129u
ru: po/bin/ru.po: 200t1f1u
sl: po/bin/sl.po: 200t1f1u
sv: po/bin/sv.po: 185t1f16u
uk: po/bin/uk.po: 200t1f1u
uz: po/bin/uz.po: 5t7f190u
vi: po/bin/vi.po: 185t1f16u
zh_CN: po/bin/zh_CN.po: 11t11f180u
zh_HK: po/bin/zh_HK.po: 15t24f163u
po/pod (pot: 289734)
ca: po/pod/ca.po: 891t86f478u
de: po/pod/de.po: 1455t
es: po/pod/es.po: 1455t
fr: po/pod/fr.po: 1450t1f4u
it: po/pod/it.po: 374t85f996u
ja: po/pod/ja.po: 1450t1f4u
pl: po/pod/pl.po: 1450t1f4u
ru: po/pod/ru.po: 437t31f987u
Thanks,
Denis
5:09 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
On 2012/10/4 D. Barbier wrote:
On 2012/9/18 D. Barbier wrote:
[...]
> I will soon update PO files so that you can translate documentation
> about these new options.
[...]
Hello,
I would like to release po4a 0.43 on 17th, October, please update your
translations.
Here are current PO stats:
[...]
... and I also prepared in advance PO files to generate HTML pages served at
http://po4a.alioth.debian.org/
after making the release. There is no deadline, these HTML pages can
be generated at any time.
PO files can be found by replacing po4a/trunk by po4a/web in the SVN location.
Denis
7:45 a.m.
New subject: [Po4a-devel] New --porefs option, call to translations coming soon, po4a-buid retired
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
Le 03/10/2012 19:23, D. Barbier a écrit :
Here are current PO stats:
Some of them are almost useless (less than 5 translated messages over
200), and I propose to simply remove them unless there is a good reason
to keep them:
bn: po/bin/bn.po: 3t9f190u
he: po/bin/he.po: 3t9f190u
ku: po/bin/ku.po: 4t8f190u
oc: po/bin/oc.po: 4t20f178u
(The previous translator just
wrote me he was tired being alone and
stopped software translation into Occitan).
uz: po/bin/uz.po: 5t7f190u
Regards
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQcCfOAAoJELgqIXr9/gnyTDkP/jh5qHyDiScE8QGJiFhbuPH5
U+qiVbfmqrSIt6HcydT5A0n8c9h8nFGxt2eC/CqK4HhCQF8ZzR0TJIY4nJhcDK/3
QtRN0hc4N7Zy/Y6OQ1vnDK4GXjLIgW/yjjO4eVIxvu71ru2XMAia/PhGJ6hXt4Mz
2m4mNL0/MO9HHyphEsxoo7OwnaG63xDOQ28Rg5V5meqHJggkBRgbSxM9+oVWNPPt
woCaxv/pR6pcLxhXDr+RsEwj6btomblGB2H/Vtd7LHFwu79a5rcCPeLCslrjgbzY
A9Kwu2j6CtbXsyESXEAHpYXhRnqC5ST7XSFYvpVPeDXsM7cWF4ZgwzjMt62Cee8G
AadVLBLaJEbp/t7wd3NmUzeCr3HIMH1MQF7gD2Ij11uikAp7QJdV4XGtN+mcbDF/
HsRmZb2Luwuw8eygxwK/aHKw7mAuk7W+9uO81m7iYxXMGxOGr05GiL3xS5Z9EbJZ
ONLr5Z52C/KizvBaBlyedeWAhIVTxIPph3Fj1/13hmZvwiVRSHSMJVh0h+NcVTv8
2A9egRlMLjPOrNf+HeMGyYSLw8yMBgWwj9kx/7nRbjYIYG7vBRF3ZbVkjjDlx4qg
FxSJbjniLXbVXdJsYIBefMEMbcAO+/+S84vSuyd7oZ1tTuTz3Wln2Gcec/qvgUf3
mObFpi39NnCXe4xcSJ6K
=FG74
-----END PGP SIGNATURE-----
4229
days inactive
4248
days old
7 comments
3 participants
participants (3)
-
D. Barbier -
David Prévot -
Neil Williams