summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2023-03-16 00:11:20 +0100
committerBruno Haible <bruno@clisp.org>2023-03-16 00:11:20 +0100
commit6fabdc10e3fe51d660517c42da6217d63071f32b (patch)
tree5bd318c50f59ef5adf5cf67eae8528491205ac93
parenteea9d109d1eb81d5ea2e5e63848d9b123073a238 (diff)
downloadgettext-6fabdc10e3fe51d660517c42da6217d63071f32b.tar.gz
doc: Add a clarification.
Reported by Christian Ohm <chr.ohm@gmx.net> in <https://savannah.gnu.org/bugs/?36084>. * gettext-tools/doc/gettext.texi (c-format Flag): Clarify that an xgettext:... comment applies only to the next string.
-rw-r--r--gettext-tools/doc/gettext.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index d50b96969..610b3960e 100644
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -2648,7 +2648,9 @@ the @code{c-format} flag. This kind of comment should be used when
@code{xgettext} does not recognize the string as a format string but
it really is one and it should be tested. Please note that when the
comment is in the same line as the @code{gettext} keyword, it must be
-before the string to be translated.
+before the string to be translated. Also note that a comment such as
+@code{xgettext:c-format} applies only to the first string in the same
+or the next line, not to multiple strings.
This situation happens quite often. The @code{printf} function is often
called with strings which do not contain a format specifier. Of course