I'm using Po4a for maintenance of reST(reStructuredText) formatted
The format "text" is almost working fine here but has problems with some
of reST's specials.
So I patched Text.pm to get it working, at least for me.
Since I'm new to Po4a (and to this list) and not fluent in Perl
it may not be a perfect solution, but anyway:
Is there any interest in the patch (it's against version 0.42)?
I will give a talk about po4a at the end of November, it may include new
features like Asciidoc. So I want to make a new release before that date.
Here is my current planning:
* Now: bugfixes and proofreading of documentation
* Sunday, 12 Nov: string freeze
* Wed, 21 Nov: release
I just updated PO files; please review the new strings and help me to
-----BEGIN PGP SIGNED MESSAGE-----
Le 20/11/2012 10:12, Osamu Aoki a écrit :
> Maybe, simplest thing to do is use tags with attribute in the original
> XML file ... like:
> <screen translate="no">...</screen>
Sure, would be nice to push that in a higher level (i.e. po4a).
> <filename translate="no">...</filename>
Note sure how useful it would be for inline stuff on the other hand.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
I have a problem with the usage of po4a.
My master-document "iuf-rulebook.tex" is in the folder "src".
I already generated a template "iuf-rulebook.pot" in "po".
Translated po-files should go into the po-folder, while translated
tex-files should be generated in the the folder "translated".
Makefile out po po4a.cfg README.md src translated
$ ls src
$ ls po
$ ls translated
$ cat po4a.cfg
[type: latex] src/iuf-rulebook.tex $lang:translated/iuf-rulebook-$lang.tex
$ TEXINPUTS=src: po4a po4a.cfg
po4a.cfg:1: no pot-files found in po/
po4a Version 0.40.2
1. When I run po4a, it tells me, that there are no pot-files in the
po-directory. What am I doing wrong here?
2. Can po4a also generate the pot-files, or do I have to do this
exclusively with po4a-gettextize?
Thanks a lot!
Dear po4a team,
I'd like to renew the workflow of the rulebook of the international
unicycling federation. It's a big document (~100 pages) with competition
rules for unicycling. It is constantly changing, because the sport is very
young and developed a lot. Sadly there is no space for experimental rules
that need to be tested first.
Right now it is written in MSWord, passed around by email and the
translations are not coordinated very well. This worked out for the last 10
years, but I think today we can do much better.
How I think it should work:
- Many people should be able to write differnt parts of the document at the
- People need to know what changed at which time, so we need version control
- There should be versions with experimental rulesets for testing
- If an experimental rule works out, it can be merged into the master
- The translation should be done collaboratively by the community
- people should be able to view the current versions (including
translations) online and/or print them
- If a change to a master/experimental document is made, the translation
system is automatically updated, so that the community can start to
translate changes immediately. (No regular admin interaction)
Here are my ideas so far:
- Rewrite the whole thing in LaTeX (can render to HTML or PDF)
- Put it in a git repository and manage experimental versions as branches
- With every commit render the pdf and html versions.
- Translate it (and also the experimental branches) collaboratively with
po4a and Pootle and also render the translated documents automatically
I think this could solve the issue. But before we start to work I want to
know if this is the right approach. Latex and git are no problem. But for
the translation I'm not sure.
With a new commit in git, we could trigger a po4a-updatepo for the changed
latex files in every branch. But is it possible to automatically reinject
them into Pootle? How do the translations flow back from Pootle to the
build system. If a new language is set up in Pootle, how does it create new
documents? Can we do version control for the languages to be able to jump
back to an older version of a document with proper translation?
I guess you can answer these questions easily and support us to set this up
Thanks in advance and greetings from Germany
International Unicycling Federation