4:26 a.m.
Hello,
As told during the preparation of po4a 0.40, I would like to propose a
longer string freeze for 0.40.1, but also to release 0.40.1 as soon as
possible. I will try to release po4a 0.40.1 on Wednesday, 25th August
around 20:00 UTC. That sounds reasonable, but not very exciting; in
order to make this experience funnier, I will leave on vacation very
soon and do not know whether I will read mails ;-)
Omar, can you please send calls for translations as you did with 0.40?
First set a string freeze date with David, I do not know if all the
stylistic changes in English documentation he proposed have been
applied. if you will not have time, can you please explain how to
proceed so that someone else can do this job?
Thanks in advance.
Denis
6:26 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
As told during the preparation of po4a 0.40, I would like to propose
a
longer string freeze for 0.40.1, but also to release 0.40.1 as soon as
possible. I will try to release po4a 0.40.1 on Wednesday, 25th August
around 20:00 UTC. That sounds reasonable, but not very exciting; in
order to make this experience funnier, I will leave on vacation very
soon and do not know whether I will read mails ;-)
Omar, can you please send calls for translations as you did with 0.40?
First set a string freeze date with David, I do not know if all the
stylistic changes in English documentation he proposed have been
applied. if you will not have time, can you please explain how to
proceed so that someone else can do this job?
I will be available. Despite some _short_ trips to the beach, I will be
around, so I'll send that call.
I think all stylistic changes have been applied. However, I'm in the
process of reviewing my own Spanish translation and I caught one or two
things that may be changed in the original docs. Hopefully I will be
finished in a couple of days.
Once that is done, I will set a date with David if he thinks all his
changes made it into the sources.
Regards,
--
Omar Campagne Polaino
noon
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 30/07/2010 07:26, Omar Campagne a écrit :
> First set a string freeze date with David, I do not know if all
the
> stylistic changes in English documentation he proposed have been
> applied. if you will not have time, can you please explain how to
> proceed so that someone else can do this job?
I will be available. Despite some _short_ trips to the beach, I will be
around, so I'll send that call.
I think all stylistic changes have been applied. However, I'm in the
Same here, anyway, I may have missed a few details.
process of reviewing my own Spanish translation and I caught one or
two
things that may be changed in the original docs. Hopefully I will be
finished in a couple of days.
Please, commit your changes, I plan on doing (again) a review tonight.
Once that is done, I will set a date with David if he thinks all his
changes made it into the sources.
If no one else plan on reviewing, I think it will be quite ready this
weekend, maybe earlier if you prefer but keeping the weekend if we spot
some more details could be fine. Let's propose Monday, 2nd August around
8:00 AM UTC for a string freeze.
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxTBSwACgkQ18/WetbTC/qvTQCeNIsVOz4DfwF8IWbbMLrwxzXD
brcAnAgfogXNYdDn8WV34ww2gN5A/zA1
=5zdz
-----END PGP SIGNATURE-----
12:53 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
On 2010/7/30 David Prévot wrote:
[...]
If no one else plan on reviewing, I think it will be quite ready
this
weekend, maybe earlier if you prefer but keeping the weekend if we spot
some more details could be fine. Let's propose Monday, 2nd August around
8:00 AM UTC for a string freeze.
I made changes in the header entry of POT files, but did not
regenerate PO files to not cause conflicts.
When syncing PO files, could someone please also update the new Language field?
Something like this should work just fine:
for f in po/*/*.po; do
sed -i -e "s/^\"Language: \\\\n\"/\"Language: $(basename
${f%.po})\\\\n\"/" $f
done
Thanks
Denis
3:12 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 30/07/2010 13:53, Denis Barbier a écrit :
On 2010/7/30 David Prévot wrote:
[...]
> If no one else plan on reviewing, I think it will be quite ready this
> weekend, maybe earlier if you prefer but keeping the weekend if we spot
> some more details could be fine. Let's propose Monday, 2nd August around
> 8:00 AM UTC for a string freeze.
I made changes in the header entry of POT files, but did not
regenerate PO files to not cause conflicts.
When syncing PO files, could someone please also update the new Language field?
Done, I also made a last round of preventive unfuzzy for po/pod
(corrected some more style stuff in the process). Omar seems to have
unfuzzy everything po/bin (just added the s/ascii/ASCII/ one). I now
plan to have a second look in html...
(As a translator, I like to work with PO files, that's why I regenerated
them, but feel free to continue and correct some more stuff before the
call for translation).
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxUg58ACgkQ18/WetbTC/oKtQCaArCsMGT/TCkQTFJDETOsXZCO
1QsAoJlRx7VpQ6EsWNNGCl8KTIrRQ8AF
=4vkC
-----END PGP SIGNATURE-----
3:39 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
Done, I also made a last round of preventive unfuzzy for po/pod
(corrected some more style stuff in the process). Omar seems to have
unfuzzy everything po/bin (just added the s/ascii/ASCII/ one). I now
Hi, I
didn't unfuzzy all po/bin files from the first correction. Will do
the remaining ones tomorrow morning. I already finished my own Spanish
correction, and I did insert the corrections I could find in the
English docs but for the one below.
Please, search for
"docbook-xsl - the stylesheet"
in the po(t) file.
It will take you to string which may look better with "the default
stylesheet" though I was unsure about that correction.
plan to have a second look in html...
(As a translator, I like to work with PO files, that's why I
regenerated
them, but feel free to continue and correct some more stuff before the
call for translation).
Ok, thanks.
I will notify docs translators about the stylistc changes, as they have
a long deadline, and as they may have, i.e. "po" in their msgtrs where
"PO" appeared in msgids, previous to your corrections (hence unnoticed
to us as they weren't marked fuzzy). I had to correct such things
during my Spanish review.
Saludos,
--
Omar Campagne Polaino
6:03 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 31/07/2010 16:39, Omar Campagne a écrit :
I did insert the corrections I could find in the
English docs but for the one below.
Please, search for
"docbook-xsl - the stylesheet"
in the po(t) file.
FWI, the complete sentence (form po4a-build.conf.5.pod) currently
associated is:
Manpages are generated using default support in docbook-xsl - the
stylesheet used can be overridden using the C<XSLFILE> setting in the
C<po4a-build> configuration file."
It will take you to string which may look better with "the
default
stylesheet" though I was unsure about that correction.
I don't what's best (I don't think, after verifying, I made any change
to that sentence), but I don't think adding "default" a second time to
that sentence would make it any better.
Actually, we may just change the following line around line 41 from
Locale::Po4a::Chooser:
$modname = ucfirst($module);
to something like:
$modname = ucfirst(lc($module));
(or maybe better: put $module earlier in lowercase, around line 23) in
order to accept case-insensitive module name, and not to bother with
calling, e.g. the po4a Xml (or xml) module to handle XML documents, and
also permit the usage of the XML" module (and permit the use of "XML" in
config files).
Anyway, I'm going to update PO and POT files (again), it seems I didn't
succeed in my last commits, I'll check carefully.
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxV/ToACgkQ18/WetbTC/p6wwCeJQm2DjbF6Y+1WRzXYb83Wtvk
mG0AnihbmrqiSLqAvQ5S7cOkLKqIN3AZ
=cPKZ
-----END PGP SIGNATURE-----
9:49 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
I don't what's best (I don't think, after verifying, I
made any change
to that sentence), but I don't think adding "default" a second time to
that sentence would make it any better.
Ok.
Actually, we may just change the following line around line 41 from
Locale::Po4a::Chooser:
$modname = ucfirst($module);
to something like:
$modname = ucfirst(lc($module));
(or maybe better: put $module earlier in lowercase, around line 23)
in
order to accept case-insensitive module name, and not to bother with
calling, e.g. the po4a Xml (or xml) module to handle XML documents, and
also permit the usage of the XML" module (and permit the use of "XML" in
config files).
Wow, that's Chinese to me :-) I'm going through basic bash
scripting as
of now.
Anyway, I'm going to update PO and POT files (again), it seems I
didn't
succeed in my last commits, I'll check carefully.
Great. I'll issue a call
for translations once the PO/POT files are uploaded
and preventive unfuzzying is done.
Thanks,
--
Omar Campagne Polaino
10:33 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 02/08/2010 10:49, Omar Campagne a écrit :
> Anyway, I'm going to update PO and POT files (again), it
seems I didn't
> succeed in my last commits, I'll check carefully.
Great. I'll issue a call for translations once the PO/POT files
are uploaded
and preventive unfuzzying is done.
I did the last preventive unfuzzy for /po/pod yesterday, but it seems
Nozomu didn't work on the last version of it to unfuzzy (there might
have been only few double work, so it's fine I guess):
- -"POT-Creation-Date: 2010-07-31 12:10-0400\n"
+"POT-Creation-Date: 2010-07-31 11:17-0400\n"
But as far as I can see Nozomu's update of po/bin/ja.po, it seems that
we didn't finished preventive unfuzzy every where in po/bin/. It's not
that big (a few strigs only compared to thousands already unfuzzy in
/po/pod), so we may let it this work to translators, but if we want to
provide fully unfuzzy PO files, Omar, please tell me which files of
po/bin/ you completed, in order to finish what's left (I didn't touch
them myself, except in order to perform preventive unfuzzy for the last
items I modified, and the French one).
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxW5TwACgkQ18/WetbTC/qDagCfbQN5YP91tneKYRY4h0sD9FEp
CwIAnjNgZ7ozZ9BiyXfjKPaIffHOs3HL
=4mMM
-----END PGP SIGNATURE-----
4:33 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
Hello, David
Did I make a mistake in anything?
Was I too early?
I will work again to po/bin/ja.po.
Regards
Nozomu
--
+--------------------------------------------------------+
KURASAWA Nozomu (nabetaro) <nabetaro @ caldron.jp>
GnuPG FingerPrint:
C4E5 7063 FD75 02EB E71D 559B ECF6 B9D2 8147 ADFB
+--------------------------------------------------------+
6:07 p.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 02/08/2010 17:33, nabetaro(a)caldron.jp a écrit :
Hello, David
Hi Nozomu,
Did I make a mistake in anything?
On the contrary, thanks for your quick update: it made me realize that
we haven't done all the preventive unfuzzy I planed before asking for
translation.
It's up to Omar now, to ask for help if some PO files from po/bin/ need
to be unfuzzy (I didn't kept track of which files Omar has already
worked), and call for translation once he is ready.
Was I too early?
Quite a perfect timing actually (well, I may have saved you one more
string if you got the documentation translation file one hour later, but
it doesn't matter).
Since anyway, as planed, the string are freezed now, it happens that
Japanese translation is ready, thanks for that.
I will work again to po/bin/ja.po.
It's up to you: Denis planned to release on Wednesday, 25th August
around 20:00 UTC, so feel free to improve your translation until there.
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxXT54ACgkQ18/WetbTC/qqCgCdHxUrnV7Py9Wjn1H1D631Z00e
N1sAoIaU13tPH7IBeKCMfrZkGac4CYb5
=yDvc
-----END PGP SIGNATURE-----
4:49 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
But as far as I can see Nozomu's update of po/bin/ja.po, it seems
that
we didn't finished preventive unfuzzy every where in po/bin/. It's not
that big (a few strigs only compared to thousands already unfuzzy in
/po/pod), so we may let it this work to translators, but if we want to
provide fully unfuzzy PO files, Omar, please tell me which files of
po/bin/ you completed, in order to finish what's left (I didn't touch
them myself, except in order to perform preventive unfuzzy for the
last items I modified, and the French one).
Concerning po/bin, I basically
unfuzzied all I could without breaking
anything. This means, I didn't touch some files with really strange
characters, neither strings where «pot» also has a meaning in that
language which could lead to confusion. There shouldn't be a need to
touch those files now (unless a new fuzzy gets in).
Fully unfuzzy is also kinda imposible, given the old state of some
files. I think po/bin is ready for the call for translations, whereas
po/pod still needs to get those last minute corrections (I think po/pod
files haven't been updated with those weekend changes). Have you been
able to commit to the repo those changes?
Cheers
--
Omar Campagne Polaino
9:32 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 03/08/2010 05:49, Omar Campagne a écrit :
Concerning po/bin, I basically unfuzzied all I could without
breaking
anything. This means, I didn't touch some files with really strange
characters, neither strings where «pot» also has a meaning in that
Sure. Weird characters are fine sometime (it's easy to spot the Latin
characters ;-), and I think po or pot means something in Polish (I
manage to learn how "file" and "files" are translated in order to
unfuzzy where it was possible in po/pod), so I guess it's fine (anyway,
there are not lots of fuzzy in po/bin, and plenty of time until August,
25th).
files. I think po/bin is ready for the call for translations,
whereas
po/pod still needs to get those last minute corrections (I think po/pod
files haven't been updated with those weekend changes). Have you been
able to commit to the repo those changes?
Sure, it's ready to call for translation as far I can tell (yes, I
updated and unfuzzy the last minutes changes of this week-end).
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxYKHQACgkQ18/WetbTC/oZpQCeMw5sf+ROONkgoklBkh5XP5sP
ZecAnAv+gMoERPHzoFyRYQRBbVcwf3Xw
=6wfz
-----END PGP SIGNATURE-----
9:21 a.m.
New subject: [Po4a-devel] Preparation of the next po4a 0.40.1 release
On 2010/7/30 Denis Barbier wrote:
Hello,
As told during the preparation of po4a 0.40, I would like to propose a
longer string freeze for 0.40.1, but also to release 0.40.1 as soon as
possible. I will try to release po4a 0.40.1 on Wednesday, 25th August
around 20:00 UTC. That sounds reasonable, but not very exciting; in
order to make this experience funnier, I will leave on vacation very
soon and do not know whether I will read mails ;-)
Omar, can you please send calls for translations as you did with 0.40?
First set a string freeze date with David, I do not know if all the
stylistic changes in English documentation he proposed have been
applied. if you will not have time, can you please explain how to
proceed so that someone else can do this job?
Thanks in advance.
Hello,
I have been mostly away from computers during my holidays, but David
and Omar (thanks!) did a great job and we should be able to release
0.40.1 as planned; there is no problem than I am aware of with current
CVS.
Denis
4998
days inactive
5013
days old
13 comments
4 participants
participants (4)
-
David Prévot -
Denis Barbier -
nabetaro＠caldron.jp -
Omar Campagne