From b266a406877b46ab0197d3c7da8c457c305f29be Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 5 Jan 2021 14:26:37 -0500 Subject: [PATCH] doc: improve NLS instruction wording Reported-by: "Tang, Haiying" Discussion: https://postgr.es/m/bbbccf7a3c2d436e85d45869d612fd6b@G08CNEXMBPEKD05.g08.fujitsu.local Author: "Tang, Haiying" Backpatch-through: 9.5 --- doc/src/sgml/nls.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml index 3764d49f62..d49f44f3f2 100644 --- a/doc/src/sgml/nls.sgml +++ b/doc/src/sgml/nls.sgml @@ -90,7 +90,7 @@ msgstr "another translated" ... - The msgid's are extracted from the program source. (They need not + The msgid lines are extracted from the program source. (They need not be, but this is the most common way.) The msgstr lines are initially empty and are filled in with useful strings by the translator. The strings can contain C-style escape characters and @@ -113,7 +113,7 @@ msgstr "another translated" The #. style comments are extracted from the source file where the message is used. Possibly the programmer has inserted information for the translator, such as about expected alignment. The #: - comment indicates the exact location(s) where the message is used + comments indicate the exact locations where the message is used in the source. The translator need not look at the program source, but can if there is doubt about the correct translation. The #, comments contain flags that describe the