Re: [Po4a-devel] Bug#594831: debian-faq: Please, add po4a support
by David Prévot
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[Keeping the DDP mailing list CCed, and add the po4a developer list if
someone wants to correct me or add other hints, don't hesitate to ask
directly on po4a-devel of you have any problem.]
Le 31/08/2010 14:54, Javier Fernández-Sanguino Peña a écrit :
> On Sun, Aug 29, 2010 at 08:38:08PM -0400, David Prévot wrote:
>> Please find attach a short patch in order to permit this, at least
>> for the French translation. Note that this patch doesn't force to
>> use a PO files for every languages, and no Makefile will need to
>> be edited if another language decide to use a PO file as well.
>
> Thanks for the patch, it is very welcome. Switching to the use of po4a is one
> of the things I want to do with all the documentation I maintain in the DDP.
Great, I'm willing to help you in this task if you want, this remarks
applies to others documentations as well.
With Simon Paillard, we were considering to provide a template Makefile
in order to give the opportunity to have something a bit unified for the
DDP, but we also think it would be great to switch from DebianDoc to
DocBook XML (I'm not sure which one needs to be done first, probably
provide a template Makefile DocBook XML ready and a method to switch
from DebianDoc would be the best thing to do).
>> The French translation is currently beeing updated using PO file,
>> so if noone speaks against, it will be applied in the Subversion
>> repository with the up to date French translation.
>
> What tools are you using to convert the current SGML sources to PO for
> French? Is there an automatic tool that helps a little bit with this?
There is no full automatic tool to do that, but there are lots of hints
in the “HOWTO convert a pre-existing translation to po4a?” part of po4a(7).
> I would
> like to switch other languages too and I would appreciate some help there
> too.
I believe that this works needs to be done by a translator (it doesn't
need to be done directly by the translator of the document, but a
knowledge of the language translated is really helpful), since there is
a need to “adjust” the translated or original document in order to
perform the initial “gettextization”.
I just gave some more hints on the debian-l10n-french mailing list in
order to do so, may I try to translate this piece of advice here. A wiki
page may be a good place to publish it if it could be of any help (I'm
willing to edit the page, but please, give me a hint of *where* in the
wiki it should be written, I'm still a bit lost there), or even the
po4a(7) manual page (but I'm less sure: there is already a lot of
information in it, and po4a is not debian-specific).
*HOWTO perform gettextization on DDP*
1- Update each original page of the local repository to the version
present on the header of the translated document, it usually looks like
“<!-- Subversion revision of original English document "5108" -->”
and then proceed to the initial “gettextization” as explained in po4a(7)
(implies some local changes to the original or translated documentation
in order to do so, keeping those changes will be helpful for the two
last step, using “svn diff” on the translated directories might be enough).
2- Once the PO file obtained for this non up-to-date translation,
perform an automatic unfuzzy. The strings will need to be checked by the
translator, but this task can be done later:
msgattrib --clear-fuzzy file-step1.po -o file-step2.po
3- Update the original version of the documentation on the local
directory (“svn update”), and update the PO file using “po4a-updatepo”.
The PO file obtained is ready for translation update. This file can then
be sent to the official translator of the document if the three first
step were performed by someone else (eventually provide the result of
“svn diff” obtained in stage 1: sometimes the translation is a bit in
advance on its own header, so the translator may pick back what he has
already translated but was not included in the PO file).
4- Put back addenda, which are mainly used for translator credits, or
language specific stuff, and eventually provide a po4a patch for the
package if it is not yet available (which was the initial goal of this
bug report).
Cheers
David
P.-S.: Please note that some translators prefers to work using the
current workflow (using svn to provide diff of the original translation
and edit directly a translated document) rather than editing a PO file.
Unless every translator of a document are willing to use PO files (e.g.
developers-reference), it's probably best to let translator choose his
own method: it's not a problem since both method can cohabit (e.g.
maint-guide or debian-history).
P.-P.-S.: The French translation for the debian-faq was not too much
outdated, after the third stage, the PO file had the following
statistics: 951t11f10u. I think Simon (the actual translator) agrees
that it would be easier to maintain than around fifteen independent
files currently needed to build the debian-faq.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkx9dz8ACgkQ18/WetbTC/rBtACgiM8yEilGWWVhR3lrruP95bBe
N+kAn3SLj8CVlAwuFl1x2jeb7N+cHPxb
=R6MJ
-----END PGP SIGNATURE-----
13 years, 11 months
po4a 0.40.1 has been released
by Denis Barbier
Hello,
Nicolas uploaded po4a 0.40.1 yesterday, enjoy!
Many thanks to Omar and David who took care of po4a during my holidays.
===========================================================
* Major changes in release 0.40.1 (2010-08-25)
Po:
* Change header entry to be consistent with xgettext when creating
POT files: replace Content-Transfer-Encoding: ENCODING" by
"Content-Transfer-Encoding: 8bit\n" and add a Language field.
documentation:
* Improve English style (proper casing, replace cvs by VCS, etc).
translations:
* Updated French translations
* Updated Spanish translations
* Updated Japanese translations
* Updated Esperanto translations
* Updated Swedish translations
* Updated Russian translations
* Updated Estonian translations
* Updated Ukrainian translations
* Updated Czech translations
* Updated Portuguese translations
* Updated German translations
Project resources:
* We migrated from CVS to SVN. All CVS history has been converted.
See http://svn.debian.org/viewsvn/po4a/
The standard SVN layout is used (with top-level /trunk, /branches
and /tags directories), and the files to generate the website
(html/, po/html.cfg and po/www) are moved into a new /web
top-level directory.
===========================================================
Here are some tips to work with this Subversion repository, copied and
edited from
https://alioth.debian.org/scm/?group_id=30267
Anonymous Subversion Access (read-only)
svn checkout svn://svn.debian.org/svn/po4a/trunk
Developer Subversion Access via SSH (read-write, available only to
project developers)
svn checkout svn+ssh://developername@svn.debian.org/svn/po4a/trunk
Directory Layout (can be browsed onlined at http://svn.debian.org/viewsvn/po4a/)
/trunk
This is our main development branch, you should only commit there
/branches
Long standing branches, not used yet
/tags
Tags for official releases
/web
Files needed to generate the website have been moved there
As always, do *NEVER* checkout /svn/po4a, this will retrieve gigabytes
from the SVN server. You should always checkout /svn/po4a/trunk or
svn/po4a/web.
If you are interested only by po4a sources, you can run
svn checkout svn+ssh://developername@svn.debian.org/svn/po4a/trunk po4a
to create a po4a/ directory in your current directory. If you want
also to translate the web site and generate PHP files, you need /trunk
and /web and can run:
mkdir po4a
cd po4a
svn checkout svn+ssh://developername@svn.debian.org/svn/po4a/trunk
svn checkout svn+ssh://developername@svn.debian.org/svn/po4a/web
Denis
13 years, 11 months
RFC: Migrating away from CVS
by Denis Barbier
Hello,
I am currently playing with cvs2svn to convert the CVS repository into
SVN. As already told into another mail, I would like to reorganize
the directory layout when switching. The CVS repository contains 7
directories:
* po-debconf: Up-to-date sources of the po-debconf Debian package.
* po-debiandoc: Obsoleted by the Sgml module of po4a
* liblocale-po4a-perl, po-man, po-pod, Po4a: These 4 directories
have been merged into po4a 7 years ago.
* po4a: What we are interested in.
po-debiandoc has been removed from Debian servers in 2006, IMO it can
be considered as being dead and there is no reason to migrate it into
SVN.
po-debconf is alive, the question is whether it should live in the
same SVN repository.
The po4a module contains sources shipped in official tarballs,
experimental modules which are not part of official tarballs, and web
pages.
I created an experimental SVN dumpfile:
http://po4a.alioth.debian.org/svnrepo-20100815.dump.bz2
Layout is:
trunk/
po4a sources, equivalent of CVS HEAD, without web pages
tags/
corresponding to CVS tags, which have been rewritten as 0.36, 0.36.1, etc
branches/
only contain 0.19.x branch
web/
web pages
Please test and do not hesitate to give comments.
Thanks.
Denis
13 years, 11 months
Suggestion: New page on the website with links to projects using po4a
by Denis Barbier
Hello,
I am usually not a big fan of those "These projects use XXX" pages,
but as po4a is a little bit complex to start with, I believe that such
a page could be very helpful for beginners.
What do you think? Is this a stupid idea? Is someone interested by this task?
Denis
13 years, 11 months
po4a for C,C++, perl, python ?
by François Boulogne
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear all,
I discovered po4a from the french ubuntu's wiki page (and it sounds
like awesome :) ) and this page teaches us that po4a is suitable for
some languages like C, C++, perl, python (for the moment, I'm
interesting in python).
http://doc.ubuntu-fr.org/po4a#format_de_fichiers_supportes
However, I didn't find any note about this feature in the man page nor
your website. So, is it a mistake? or there is a hack to do it?
Regards.
PS: You could reply in french if English is bothering you ;)
- --
François Boulogne.
Membre de l'April - Promouvoir et défendre le logiciel libre
http://www.april.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMbSIXAAoJEKkn15fZnrRLjCoP/1S2d/acFOJ+j5sMgZtDy4tH
O4VpzC1BukopEaxCc3dpI5wxn8Nb+L0l3YhuncT13ni0Dm82lXRrs+LvqWvOvgQJ
16TRcKjJ3Yu/6hnJvtMtWMz45E3qLQ0PWQ0SxY0au2E+kbybGo5GEPhENh8y1oUj
fWtY1Fyby+afevmbPutLEgA9fKfcrMMr5vxdviOxOvIRre+45juBBbEaxPi4pFR6
TS3dYLkhd0NwjeA9M4ODE1xX2M2KZc+utHR2xygwR/EZl79XhZQdcCnGYKV87zEf
B04akyFlgH5XrG0u+f8cKvqqOQbWBg8umlcghyE/NFyvGlnwnac797iEZdGx73ua
kgTmlI3/KzHyReOLFAbEEzv3NdPflVAAE9KY4MrrLStK6bsU9I1uBf1fAcFCojOG
Lg/01lOiEa+z3MOcKiQONFPHWqJIVYWnt/g9/AdpbqM54bv6LV7yVnkV6/jfbgeW
eKgCPNvVJRHKYdG1hW7SIjFbFQ7VrOEfDj44PKIpSYykLiUEcnZNWO/M6uNnkRLM
Bt/Igh7DwTWMEkI7A09MALdwD2+QAl2R4pplUmnDqzRoUGO6BP4ZkMgqZJJ80BLI
GYJfCgVInxT63kraWA00C7QBK5u0jV9WIPlubxV7nCIWxDRlJ4aXERljPZuzYoMQ
7xIo1s0qKDdOl97R0CKc
=yMcg
-----END PGP SIGNATURE-----
13 years, 11 months
Only 7 days left before next po4a release, please update translations
by Denis Barbier
Hello,
Here are the current statistics about translations.
Some languages have only few strings to fix to be fully complete,
please make sure to update PO files before next Wednesday. I also
updated lately the po/www/*.po files which are used to build
translated pages for http://po4a.alioth.debian.org/
Maybe Catalan and Italian translators could try to provide
translations, online manual pages are already provided at
http://po4a.alioth.debian.org/man/
since they are automatically converted from po/pod/*.po files.
As usual:
t = translated messages
f = fuzzy messages
u = untranslated messages
po/bin (pot: 28K)
af: po/bin/af.po: 22t 31f 134u
ar: po/bin/ar.po: 1t 186u
bn: po/bin/bn.po: 3t 9f 175u
ca: po/bin/ca.po: 144t 14f 29u
cs: po/bin/cs.po: 187t
de: po/bin/de.po: 185t 2u
eo: po/bin/eo.po: 187t
es: po/bin/es.po: 187t
et: po/bin/et.po: 187t
eu: po/bin/eu.po: 177t 7f 3u
fr: po/bin/fr.po: 187t
he: po/bin/he.po: 3t 9f 175u
hr: po/bin/hr.po: 29t 17f 141u
id: po/bin/id.po: 126t 27f 34u
it: po/bin/it.po: 133t 22f 32u
ja: po/bin/ja.po: 187t
kn: po/bin/kn.po: 29t 36f 122u
ko: po/bin/ko.po: 16t 16f 155u
ku: po/bin/ku.po: 4t 8f 175u
nb: po/bin/nb.po: 51t 40f 96u
nl: po/bin/nl.po: 20t 15f 152u
oc: po/bin/oc.po: 4t 21f 162u
pl: po/bin/pl.po: 187t
pt: po/bin/pt.po: 184t 1f 2u
pt_BR: po/bin/pt_BR.po: 37t 37f 113u
ru: po/bin/ru.po: 187t
sl: po/bin/sl.po: 4t 19f 164u
sv: po/bin/sv.po: 187t
uk: po/bin/uk.po: 187t
uz: po/bin/uz.po: 5t 7f 175u
vi: po/bin/vi.po: 175t 9f 3u
zh_CN: po/bin/zh_CN.po: 11t 11f 165u
zh_HK: po/bin/zh_HK.po: 15t 25f 147u
po/pod (pot: 288K)
ca: po/pod/ca.po: 874t 94f 507u
es: po/pod/es.po: 1475t
fr: po/pod/fr.po: 1475t
it: po/pod/it.po: 278t 126f 1071u
ja: po/pod/ja.po: 1475t
pl: po/pod/pl.po: 1475t
ru: po/pod/ru.po: 402t 30f 1043u
po/www (pot: 20K)
es: po/www/es.po: 99t
fr: po/www/fr.po: 99t
ja: po/www/ja.po: 97t 1f 1u
pl: po/www/pl.po: 99t
ru: po/www/ru.po: 88t 1f 10u
Denis
13 years, 11 months
(Another?) problem with non braking space in end of line with Man module
by David Prévot
Hi,
Please find attach a problem I just come across while translating ps(1)
man page: a non braking space ("\\ ") on fr.po manage to be translated
in the end of the second line of pb-nbs.fr.1 with no space at all ("\").
So the resulting man page shows no space at all.
A quick look at Locale::Po4a::Man told me that non braking space ("\ ")
on end of line are already taking care of, but this seems to be another
issue, since the space (" ") following the backslash ("\") seems to have
completely disappeared.
I ask here before searching deeper (someone may have a better knowledge
about how Locale::Po4a::Man works), but if no one (else) happens to find
a solution, is it better to submit a bug in order not to forget this issue?
FWIW, i just replaced "\\ " by real non braking space in order to fix
the issue in the manual page I'm currently translating.
Cheers
David
13 years, 11 months
Preparation of the next po4a 0.40.1 release
by Denis Barbier
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
13 years, 11 months
