Remove support for pluralisation during gettext
resource translation
#10979
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change type
Purpose
SOURCE_DATE_EPOCH
is set #10949, code related tongettext
(support for n-ary / plural forms of translated text) was modified in the codebase, and following on from that, I spent some time investigating whether that's used. It doesn't appear to be, so this pull request offers a possible cleanup by removing thengettext
referenceDetail
ngettext
allows an application to provide a dynamic number (often a count of items, like '5' inthe linter produced 5 warnings
) to the translation query so that a plurality-relevant message can be retrieved from the catalogsphinx
has previously used this within its own codebase, but no longer does --babel
command-line extraction is used to retrieve translatable resources from the codebase, and extraction of plural-form keywords is not configured (nor easy to enable, as far as I could tell)Relates
SOURCE_DATE_EPOCH
is set #10949