docs: 2.3.0 release notes trimmed, public docs cover the CJK stops and the declared-order rule - #524
Merged
Merged
Conversation
…tion section for the input-shapes notation The 2.3.0 block stood at 3,429 words against 2.2.0's 4,492 after its own trim; it is 2,527 now. Cut, by the 2.2.0 standard: every per-bullet differential-corpus count (the 2.2.0 entry carries none), edge cases narrow enough to have earned a sentence only in the design entry (Sir John Prof., Smith Sir., the V。 numeral, the one revise() round-trip residual), and rationale with no caller action (the 2019 bulk-import provenance; the lord/lady peerage argument reduced to one clause). Every example kept was re-run on the tree. The bold leads are unchanged and render without markup leaks. The Documentation section records what #469 (PRs #482, #488) added to usage.rst and customize.rst: forms 4-7 beside the three Latin shapes, the tolerated designation for a comma or Latin wrapper around a CJK name, and the form-2/form-4 correspondence. Behavior unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… family-first order stands down the patronymic rotations Two 2.3.0 behavior changes had a release bullet and no public-doc coverage (#322, #323, #384). usage.rst's "Decomposed text" section gains the vocabulary-lookup half of NFC composition, and "Honorifics come off first" gains the three wide stops reaching the honorific vocabulary plus one doctest for a period glued to a name word. The pack warning box in locales.rst, the patronymic_rules row in customize.rst and the Policy.patronymic_rules field docstring (autodoc-rendered) each carry one sentence on the declared order winning. The Lexicon pickle incompatibility stays in the release log only: no public page discusses pickling a Lexicon. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…egment consumes upstream Measured per the release checklist's "Reads:" check: classify never accesses lexicon.surnames or lexicon.honorific_tails; script_segment reads both before classify runs. Pre-existing, not a 2.3 regression. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #524 +/- ##
=======================================
Coverage 98.67% 98.67%
=======================================
Files 45 45
Lines 3320 3320
=======================================
Hits 3276 3276
Misses 44 44 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Release prep for 2.3.0, docs only. The audit behind it: every v2.3 milestone issue and every PR merged since v2.2.0 is cited in the 2.3.0 block by issue or closing PR, so the log had no gaps; the public docs had two.
What changes
Release log. The 2.3.0 block goes from 3,429 to 2,527 words, cut to the 2.2.0 standard: per-bullet corpus counts, edge cases that belong to the design entry, and rationale with no caller action. Every kept example was re-run on the tree; the bold leads render without markup leaks. A Documentation section records the input-shapes notation #469 added (forms 4-7, tolerated CJK wrappers, the form-2/4 correspondence).
Public docs. usage.rst now covers the any-width full stop and NFD vocabulary lookup (#322, #323); locales.rst, customize.rst and the
Policy.patronymic_rulesreference say a declared family-first order stands down the rotations (#384). One doctest added.Pipeline header. classify's
Reads:line no longer claims the two Lexicon fields script_segment consumes upstream. Pre-existing.Verification
doctest on usage/locales/customize: pass.
sphinx-build -W: clean. pytest: 7815 passed, 177 skipped, 4 xfailed. ruff, mypy: clean. No parser behavior changes.🤖 Generated with Claude Code