From: Bruno Haible Date: Sun, 3 Jul 2022 09:16:27 +0000 (+0200) Subject: doc: Clarify constraints for PO files. X-Git-Tag: v0.21.1~9 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=647a64f1973bbd69e6dc3540d851896c4cdaadff;p=thirdparty%2Fgettext.git 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 b9aa7798f..b5a386e32 100644 --- a/gettext-tools/doc/gettext.texi +++ b/gettext-tools/doc/gettext.texi @@ -1823,8 +1823,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: