Junio C Hamano <gits...@pobox.com> writes:
> Documentation/CodingGuidelines may want to have a sentence of two to
> explain this, though.
After re-reading what I sent out, I realized that the way I singled
out multi-line comments was misleading. Here is an updated version.
-- >8 --
Subject: [PATCH] i18n: mention "TRANSLATORS:" marker in
These comments have to have "TRANSLATORS: " at the very beginning
and have to deviate from the usual multi-line comment formatting
Signed-off-by: Junio C Hamano <gits...@pobox.com>
Documentation/CodingGuidelines | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index dab5c61..f9b8bff 100644
@@ -164,6 +164,16 @@ For C programs:
* multi-line comment.
+ Note however that a comment that explains a translatable string to
+ translators uses a convention of starting with a magic token
+ "TRANSLATORS: " immediately after the opening delimiter, even when
+ it spans multiple lines. We do not add an asterisk at the beginning
+ of each line, either. E.g.
+ /* TRANSLATORS: here is a comment that explains the string
+ to be translated, that follows immediately after it */
+ _("Here is a translatable string explained by the above.");
- Double negation is often harder to understand than no negation
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html