Fix newly-fuzzy strings in optparse.po and uuid.po (CPython 3.14 sync) - #74
Merged
sepehr-rs merged 1 commit intoSep 27, 2026
Merged
Conversation
… sync optparse.po: the getopt/optparse/argparse comparison strings dropped their trailing "included in the standard library since Python X" clauses upstream; trim the same clauses from the Persian translations. uuid.po: "a string of N bytes" was reworded upstream to "an N-byte :class:`bytes` object" for precision; update the four affected translations (including the code example comment) to match, using the existing "شیء :class:`bytes`" convention used elsewhere in this translation project. Both files pass msgfmt --check and scripts/check_markup.py.
Collaborator
|
Thanks a lot for the contribution! While some parts of the changes appear to be AI-assisted and the PR template was not followed, the scope of the changes is appropriate and the PR is good to merge. Thanks again for your work! |
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.
What
Fixes #73 — the 7 strings the sync bot flagged as newly fuzzy after the CPython 3.14 sync (commit f27c61a).
library/optparse.po(3 strings): thegetopt/optparse/argparsecomparison sentences dropped their trailing "included in the standard library since Python X" clauses upstream. Trimmed the same clauses from the Persian translations to match.library/uuid.po(4 strings): "a string of N bytes" was reworded upstream to "an N-byte:class:bytesobject" for precision (including the `# make a UUID from a 16-byte ...` code comment). Updated the four affected translations to match, using the `شیء :class:`bytesphrasing already used consistently elsewhere in this project (asyncio-subprocess.po, bz2.po, codecs.po, etc.) for the same English phrase.Validation
msgfmt --checkpasses on both filesscripts/check_markup.py library/optparse.po library/uuid.po→ "No markup mismatches found."fuzzymarkers remain in either file