From 4b6f1698539ae5a24f79c87787b29385b785631a Mon Sep 17 00:00:00 2001 From: Andreas Stricker Date: Wed, 13 Mar 2013 06:10:25 +0900 Subject: [PATCH] Describe the header entry in the PO format --- gettext-tools/doc/ChangeLog | 4 ++++ gettext-tools/doc/gettext.texi | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog index a7f5dc16a..c39b2a0be 100644 --- a/gettext-tools/doc/ChangeLog +++ b/gettext-tools/doc/ChangeLog @@ -1,3 +1,7 @@ +2013-03-12 Andreas Stricker (tiny change) + + * msgfmt.texi (PO Format): A note about the header entry + 2013-02-15 Daiki Ueno * 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 3eed8aca9..6301094e2 100644 --- 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 -- 2.47.2