Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit155bfbb

Browse files
committed
doc: improve NLS instruction wording
Reported-by: "Tang, Haiying"Discussion:https://postgr.es/m/bbbccf7a3c2d436e85d45869d612fd6b@G08CNEXMBPEKD05.g08.fujitsu.localAuthor: "Tang, Haiying"Backpatch-through: 9.5
1 parent651a557 commit155bfbb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/nls.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ msgstr "another translated"
9090

9191
...
9292
</programlisting>
93-
The msgid's are extracted from the program source. (They need not
93+
The msgid lines are extracted from the program source. (They need not
9494
be, but this is the most common way.) The msgstr lines are
9595
initially empty and are filled in with useful strings by the
9696
translator. The strings can contain C-style escape characters and
@@ -113,7 +113,7 @@ msgstr "another translated"
113113
The #. style comments are extracted from the source file where the
114114
message is used. Possibly the programmer has inserted information
115115
for the translator, such as about expected alignment. The #:
116-
comment indicates the exactlocation(s) where the message is used
116+
comments indicate the exactlocations where the message is used
117117
in the source. The translator need not look at the program
118118
source, but he can if there is doubt about the correct
119119
translation. The #, comments contain flags that describe the

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp