Rule 35 and 56 fixes for the Roman section boundary - #200
Merged
Merged
Conversation
Rule 35 keeps the number of a hyphenated Roman identifier (D-100) inside the open Roman section. The rule 69 unit boundary only recognised a digit sitting directly at the boundary, so 799cc-7 closed the section at the hyphen and reopened it, emitting a terminator and a Roman indicator that the reference does not write.
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
Contributor
Braillify testcase report
Command: |
added 2 commits
September 14, 2026 16:02
Every other job in this workflow pins the checkout to the PR head; the changepacks job did not, so under pull_request_target it read main at depth 1. changepacks compares manifests against the base branch, which a shallow checkout cannot do.
A closing quote ends the Roman section, so the parenthesis that follows sits where one attached to Hangul does and takes rule 56's Korean form. The corpus writes the Korean parenthesis there 321 times against 1. Clearing the reserved continuation lets the Roman run inside open with rule 29's indicator rather than the continuation sign.
PowerShell's Set-Content wrote a UTF-8 byte order mark, and changepacks reads the file with a parser that rejects it: 'Failed to parse changepack log ...: expected value at line 1 column 1'. Match the single-line shape the other logs already use.
Rule 29 keeps a sign attached to Roman letters inside the open section. An ampersand followed by Hangul closed the section and reopened it for its own wrapper, writing a terminator and an indicator the reference does not. The section now closes at the Hangul instead.
Contributor
Changepacksbraillify@2.1.2 → 2.2.0 - libs/braillify/Cargo.tomlMinor
Patch
braillify-c@0.1.2 → 0.2.0 - packages/c/Cargo.tomlMinor
Patch
Braillify@2.1.2 → 2.2.0 - packages/dotnet/Braillify/Braillify.csprojMinor
Patch
BraillifyNet@2.1.2 → 2.2.0 - packages/dotnet/BraillifyNet/BraillifyNet.csprojMinor
Patch
braillify@2.1.2 → 2.2.0 - packages/node/package.jsonMinor
Patch
braillify@2.1.2 → 2.2.0 - packages/python/pyproject.tomlMinor
Patch
|
Article 33's slash divides a unit from its base; it is part of article 74's digital notation only when Roman letters sit on its left. With digits alone (17.1/km, 16/32/64GB) the slash was read as an address separator and opened a Roman section, writing an indicator the reference does not.
A component of a closed compound is never a single letter, so a seam after the first letter or before the last is table noise rather than a real boundary. Article 10.11.1 read the spurious seam in whole as a boundary that the wh groupsign bridged, and spelled the word out.
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.
말뭉치 군집 분석으로 찾은 로마자 구간 경계 결함 둘을 고친다. 두 건 모두 역방향 0건이고, 한 건은 CI 워크플로 수정을 동반한다.
1. 제35항 — 단위 뒤 붙임표로 이어지는 숫자
제35항은 붙임표로 이어지는 로마자 식별자의 숫자(
D-100)를 열린 구간에 둔다. 제69항 단위 경계는 경계 자리에 숫자가 곧바로 오는 경우만 인정해서,799cc-7이 붙임표에서 구간을 닫았다가 다시 열었다.단위가 아닌 로마자(
abc-1,3ab-7)는 원래 정상이었다.cc·kg처럼 단위로 인식되는 낱말에서만 나던 결함이다.2. 제56항 — 닫는 따옴표 뒤의 괄호
닫는 따옴표는 로마자 구간을 닫으므로, 그 뒤의 여는 괄호는 한글에 바로 붙은 괄호(
모터보트(,씨넷()와 같은 자리다. 그런데 따옴표가 한글 글자가 아니라서 기존 판정을 빠져나가 UEB 괄호 ⠐⠣ 와 연속표 ⠰ 로 샜다.근거는 말뭉치 전수 집계다. 닫는 따옴표 뒤의 여는 괄호는 한국어 괄호 321 : UEB 괄호 1 이다. 예약된 연속표를 지워 괄호 안 로마자가 제29항의 로마자표로 새로 열리게 했다.
3. CI — changepacks job 의 checkout
이 워크플로의 다른 모든 job 은 checkout 을 PR head 에 고정하는데
changepacksjob 만 빠져 있었다.pull_request_target에서 PR 코드가 아닌 main 을 depth 1 로 받고 있었고, changepacks 는 base branch 와 견주므로 shallow checkout 으로는 그 비교를 할 수 없다.검증
cargo test --release -p braillify4,996 + 541 통과, clippy 통과3cal,1m는,3m/시,12km 3구간,1TB SSD,모터보트(,씨넷(CNET)과