Skip to content

Commit 786eb1b

Browse files
steadmongitster
authored andcommitted
l10n: README: call more attention to plural strings
In po/README.md, we point core developers to gettext's "Preparing Strings" documentation for advice on marking strings for translation. However, this doc doesn't really discuss the issues around plural form translation, which can make it seem that nothing special needs to be done in this case. Add a specific callout here about marking plural-form strings so that the advice later on in the README is not overlooked. Signed-off-by: Josh Steadmon <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent e9d7761 commit 786eb1b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

po/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -221,6 +221,10 @@ General advice:
221221
- Adjust the strings so that they're easy to translate. Most of the
222222
advice in `info '(gettext)Preparing Strings'` applies here.
223223

224+
- Strings referencing numbers of items may need to be split into singular and
225+
plural forms; see the Q\_() wrapper in the C sub-section below for an
226+
example.
227+
224228
- If something is unclear or ambiguous you can use a "TRANSLATORS"
225229
comment to tell the translators what to make of it. These will be
226230
extracted by xgettext(1) and put in the "po/\*.po" files, e.g. from

0 commit comments

Comments
 (0)