Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for pluralisation during gettext resource translation #10979

Conversation

jayaddison
Copy link
Contributor

Change type

  • Cleanup

Purpose

Detail

  • ngettext allows an application to provide a dynamic number (often a count of items, like '5' in the linter produced 5 warnings) to the translation query so that a plurality-relevant message can be retrieved from the catalog
  • sphinx 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)
  • As a result it seems like it may make sense to remove the code

Relates

@jayaddison jayaddison force-pushed the cleanup/translation-remove-gettext-plural-support branch from 849a0e2 to 0f723e0 Compare December 16, 2022 22:46
@AA-Turner AA-Turner changed the title Cleanup: remove support for pluralization during gettext resource translation Remove support for pluralisation during gettext resource translation Dec 29, 2022
@AA-Turner AA-Turner changed the title Remove support for pluralisation during gettext resource translation Remove support for pluralisation during gettext resource translation Dec 29, 2022
@AA-Turner AA-Turner merged commit bb37309 into sphinx-doc:master Dec 29, 2022
@AA-Turner
Copy link
Member

Thanks!

A

@jayaddison
Copy link
Contributor Author

Thanks @AA-Turner!

@jayaddison jayaddison deleted the cleanup/translation-remove-gettext-plural-support branch December 29, 2022 19:34
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants