Add Internationalization section with gettext-tstrings - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new Internationalization subsection under Libraries & Frameworks — the list currently has no i18n entry.
gettext-tstrings bridges t-strings to the existing gettext/Babel ecosystem:
_(t"Hello {name}")sends the full sentenceHello {name}to a standard PO/MO catalog, translators can reorder or repeat placeholders, and attribute access / calls / translation-side format specs are rejected. Extraction and catalog validation work with unmodifiedpybabelvia entry points. The t-string→msgid convention is specified in a versioned SPEC.md.Checked against CONTRIBUTING.md:
pip install gettext-tstrings, v0.1.0a2), MIT licensed, CI on Linux/macOS/Windows.