Repository navigation
style(i18n): remove remaining terminal punctuation from supporting copy - #1837
Merged
FresnelR27 merged 1 commit intoSep 15, 2026
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.
Problem
Supporting-copy translations still end with sentence punctuation after #1823. The remaining local removals affect strings that #1823 did not change, including authentication hints, skill scope descriptions, import progress descriptions, and regional availability notices.
Solution
Remove 299 terminal
.or。characters across 39 JSON catalogs in 13 locales: 195 integration strings, 65 project strings, and 39 session strings. Keys, interpolation placeholders, wording, internal punctuation, ellipses, and formatting are preserved. This follow-up starts from currentdevelop, which already includes #1823, and contains only the remaining punctuation changes.Potential risks
The user-visible change is limited to punctuation in supporting copy. No runtime logic, dependencies, persistence formats, or APIs change. Rendered screens were not inspected; this does not change layout rules, controls, or UI states. Reverting the commit restores the previous punctuation if needed.
Verification
pnpm run test:i18n-keys— passed, 27 tests. The initial attempt lacked TypeScript in the isolated worktree; reran successfully after linking the existing dependency installation.pnpm run check:i18n-keys— passed: zero missing keys, locale gaps, extra locale keys, placeholder mismatches, or new unused keys; 13 existing unused keys remain covered by the baseline.python3 /tmp/verify-orgii-punctuation.py— passed after commit: all 39 JSON files parse; all 299 changed values remove exactly one terminal punctuation character; keys and placeholders match; line-level comparison confirms no other content or formatting changes.git diff --check origin/develop...HEAD— passed.origin/developwas fetched before commit; the branch started at that exact revision.