Describe the header entry in the PO format

diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog
index a7f5dc16a842636195b211ec91b597d84c95f7e4..c39b2a0bea4b175664b79e5c3b9c9523e5309b93 100644 (file)
--- a/gettext-tools/doc/ChangeLog
+++ b/gettext-tools/doc/ChangeLog
@@ -1,3 +1,7 @@
+2013-03-12  Andreas Stricker  <astricker@futurelab.ch>  (tiny change)
+
+       * msgfmt.texi (PO Format): A note about the header entry
+
 2013-02-15  Daiki Ueno  <ueno@gnu.org>
 
        * msgfmt.texi (Input file location): Output file is not PO.

diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index 3eed8aca9c1b05c7ddf84eee13306ae1a6f50640..6301094e22e781b1b949215dc977884467265fb6 100644 (file)
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -1710,6 +1710,12 @@ a PO file editor, yet it may be interesting for everybody to have a better
 idea of the precise format of a PO file.  On the other hand, those
 wishing to modify PO files by hand should carefully continue reading on.
 
+An empty @var{untranslated-string} is reserved to contain the header
+entry with the meta information (@xref{Header Entry}).  This header
+entry should be the first entry of the file.  The empty
+@var{untranslated-string} is reserved for this purpose and must
+not be used anywhere else.
+
 Each of @var{untranslated-string} and @var{translated-string} respects
 the C syntax for a character string, including the surrounding quotes
 and embedded backslashed escape sequences.  When the time comes