Po4a eases translation work, and in particular the maintenance of translations, using gettext tools on areas where they were not expected like documentation.
The whole point of po4a is to make the documentation translation maintainable. The idea is to reuse the gettext methodology to this new field. Like in gettext, texts are extracted from their original locations in order to be presented in a uniform format to the translators. The classical gettext tools help them updating their works when a new release of the original comes out. But to the difference of the classical gettext model, the translations are then re-injected in the structure of the original document so that they can be processed and distributed just like the English version.
Thanks to this, discovering which parts of the document were changed and need an update becomes very easy. Another good point is that the tools will make almost all the work when the structure of the original document gets fundamentally reorganized and when some chapters are moved around, merged or split. By extracting the text to translate from the document structure, it also keeps you away from the text formatting complexity and reduces your chances to get a broken document (even if it does not completely prevent you to do so).
Project information
- Maintainer:
- Jordi Vilalta Prat
- Driver:
- Not yet selected
- Licence:
- I don't know yet
View full history Series and milestones
head series is the current focus of development.
All code Code
- Version control system:
- Bazaar
- Programming languages:
- perl
All packages Packages in Distributions
-
po4a source package in Xenial
Version 0.47-2 uploaded -
po4a source package in Trusty
Version 0.45-1 uploaded -
po4a source package in Precise
Version 0.41-1ubuntu1 uploaded -
po4a source package in Oneiric based series for Ubuntu LEB
Version 0.41-1 uploaded -
po4a source package in Mantic
Version 0.69-1 uploaded