[bug-gettext] [PATCH] Describe the header entry in the PO format section

[Andreas Stricker]

---
 gettext-tools/doc/ChangeLog    | 4 ++++
 gettext-tools/doc/gettext.texi | 5 +++++
 2 files changed, 9 insertions(+)

diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog
index a7f5dc1..2fd2ab1 100644
--- a/gettext-tools/doc/ChangeLog
+++ b/gettext-tools/doc/ChangeLog
@@ -1,3 +1,7 @@
+2013-02-15  Andreas Stricker  <address@hidden>
+
+       * msgfmt.texi (PO Format): A note about the header entry
+
 2013-02-15  Daiki Ueno  <address@hidden>
 
        * 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 3eed8ac..60b4198 100644
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -1710,6 +1710,11 @@ 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.
 
+A @code{msgid} containing an empty string @samp{""} is reserved to
+contain the header entry with the meta information. This header entry
+should be the first entry of the file. The empty 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
-- 
1.8.1.3