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 <steadmon@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Josh Steadmon committed
Dec 21, 2021 at 11:00 UTC
786eb1ba39d7bc177930f3c9b19d2989da0a7c58
1 file changed
+4
po/README.md
+4
@@ -221,6 +221,10 @@ General advice:
221
- Adjust the strings so that they're easy to translate. Most of the
222
advice in `info '(gettext)Preparing Strings'` applies here.
223
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
+
228
- If something is unclear or ambiguous you can use a "TRANSLATORS"
229
comment to tell the translators what to make of it. These will be
230
extracted by xgettext(1) and put in the "po/\*.po" files, e.g. from