From 1d726c4e469306e63ccc849ecd5aab42e5359594 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Wed, 29 May 2002 12:57:21 +0000 Subject: [PATCH] Explain xgettext output file name. --- doc/ChangeLog | 5 +++++ doc/gettext.texi | 7 +++++++ 2 files changed, 12 insertions(+) diff --git a/doc/ChangeLog b/doc/ChangeLog index a2436a046..336fbd830 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2002-05-28 Bruno Haible + + * gettext.texi (Template): Discuss the file extension. + Reported by Mark Eichin . + 2002-05-14 Bruno Haible * gettext.texi (PO Files): Add two examples. diff --git a/doc/gettext.texi b/doc/gettext.texi index 86d72c4a2..ff1366008 100644 --- a/doc/gettext.texi +++ b/doc/gettext.texi @@ -2359,6 +2359,13 @@ use this second method in this situation. After preparing the sources, the programmer creates a PO template file. This section explains how to use @code{xgettext} for this purpose. +@code{xgettext} creates a file named @file{@var{domainname}.po}. You +should then rename it to @file{@var{domainname}.pot}. (Why doesn't +@code{xgettext} create it under the name @file{@var{domainname}.pot} +right away? The answer is: for historical reasons. When @code{xgettext} +was specified, the distinction between a PO file and PO file template +was fuzzy, and the suffix @samp{.pot} wasn't in use at that time.) + @c FIXME: Rewrite. @menu -- 2.47.2