diff options
| author | Daiki Ueno <ueno@gnu.org> | 2014-05-10 16:17:56 +0900 |
|---|---|---|
| committer | Daiki Ueno <ueno@gnu.org> | 2014-05-10 16:18:35 +0900 |
| commit | 73e6ca05ebc99bd266497276abc9f4d3ac873d39 (patch) | |
| tree | 6db650f3e59e96fdd76e6b29ef25a077417104c5 | |
| parent | d778b6f43f9c7fe072688cedcf1ddaa613a7e92b (diff) | |
| download | external_gettext-73e6ca05ebc99bd266497276abc9f4d3ac873d39.zip external_gettext-73e6ca05ebc99bd266497276abc9f4d3ac873d39.tar.gz external_gettext-73e6ca05ebc99bd266497276abc9f4d3ac873d39.tar.bz2 | |
doc: Fix wording
| -rw-r--r-- | gettext-tools/doc/gettext.texi | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi index 680b420..8041f1b 100644 --- a/gettext-tools/doc/gettext.texi +++ b/gettext-tools/doc/gettext.texi @@ -8796,10 +8796,9 @@ If a POT file is absent when building, it will be generated by scanning the source files with @code{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, it won't be updated automatically, even -if the POT file is older than the source code. You can manually -update it with @code{make $(DOMAIN).pot-update}, and commit it at -certain point. +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 @code{make +$(DOMAIN).pot-update}, and commit it at certain point. Special advices for particular version control systems: |