Nicolas François <nicolas.francois(a)centraliens.net> writes:
I would use a single POT for all the files.
This will lead to an unmaintainable mess. Usually, different articles
are translated and maintained by different persons. Working with all
the strings of all articles together in a single po-file will be a
nightmare for translators.
See attached a patch I plan to commit. It adds a ontagerror
option to the Xml module, and implement multiple strategies.
Great! Using this patch and "ontagerror=reset" option makes po4a
almost perfect for the job.
I've noticed a problem with the output of po4a-translate. An empty
elements with no tag names appear where the non-matching closing tags
should be found. Here is an example:
When processed with the following commands:
$ po4a-gettextize --format xhtml -o ontagerror=reset \
--master test-case.html --po test-case.pot
$ cp test-case.pot test-case.bg.po
$ po4a-translate --format xhtml -o ontagerror=reset --keep 0 \
--master test-case.html --po test-case.bg.po \
--localized test-case.bg.html
The resulted test-case.bg.html looks like this:
As you can see, the output isn't identical to the input. The last two
closing tags are missing, replaced by strange tags without names:
10,11c10,11
< </body>
< </html>
---
</>
</>