Next: , Previous: , Up: Integrating with Version Control Systems   [Contents][Index]


13.6.3 Put PO Files under Version Control

Since translations are valuable assets as well as the source code, it would make sense to put them under version control. The GNU gettext infrastructure supports two ways to deal with translations in the context of a version controlled repository.

  1. Both POT file and PO files are committed into the repository.
  2. Only PO files are committed into the repository.

If a POT file is absent when building, it will be generated by scanning the source files with xgettext, and then the PO files are regenerated as a dependency. On the other hand, some maintainers want to keep the POT file unchanged during the development phase. So, even if a POT file is present and older than the source code, it won’t be updated automatically. You can manually update it with make $(DOMAIN).pot-update, and commit it at certain point.

Special advices for particular version control systems:


Footnotes

(6)

you can also use it through the ‘MSGMERGE_OPTIONS’ option from Makevars


Next: Invoking the autopoint Program, Previous: Files to put under version control, Up: Integrating with Version Control Systems   [Contents][Index]