doc: Clarify constraints for PO files.

* gettext-tools/doc/gettext.texi (PO Files): Mention that \u and \U escape
sequences are not allowed.

diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index 2d17df602878a713a1b9aba23c2770ac7099030e..152eb030c564af385033f3d61d38e9b84fe68e7a 100644 (file)
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -1828,8 +1828,9 @@ 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
-to write multi-line strings, one should not use escaped newlines.
+and embedded backslashed escape sequences, except that universal character
+escape sequences (@code{\u} and @code{\U}) are not allowed.  When the time
+comes to write multi-line strings, one should not use escaped newlines.
 Instead, a closing quote should follow the last character on the
 line to be continued, and an opening quote should resume the string
 at the beginning of the following PO file line.  For example: