Skip to content

fix(catalog): use OverPy zh-CN spellings for Break and Is Firing Secondary - #295

Merged
Teakowa merged 1 commit into
mainfrom
fix/zh-cn-break-firing-secondary
Sep 25, 2026
Merged

Teakowa merged 1 commit into
mainfrom
fix/zh-cn-break-firing-secondary

Conversation

@e54-bot

@e54-bot e54-bot commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Found by re-running the Bastion build diff (Wright 0.2.36 vs pinned OverPy 9.7.10, zh-CN):

  • OverPy emits 中断 for break. The catalog treated 中断 as an Abort alias and named Break 跳出循环, so Bastion's only break came out as 跳出循环 via Wright and as 中止 (Abort) after a workshop-rs re-emit of the OverPy output.
  • OverPy emits 正在使用辅助武器 for Is Firing Secondary; the catalog held that spelling on the isFiringSecondaryFire identity and named isFiringSecondary 正在发射辅助攻击.

Changes: 中断 is Break's spelling (跳出循环 kept as a parse alias); 正在使用辅助武器 is Is Firing Secondary's spelling (正在发射辅助攻击 kept as a parse alias) and is removed from isFiringSecondaryFire, which now has no zh-CN spelling. The old alias-conflict test is replaced by tests for the new mapping; digest pin and source attribution updated.

Verification: fmt, clippy, workspace tests, workshop-catalog-gen check pass. With this change patched into Wright, Bastion main.opy (zh-CN) compiled by Wright vs OverPy differs canonically by one line (开始限制阈值 假 vs 0, unrelated); before it was four differing lines.

…ndary

The zh-CN spelling 中断 is Break in the pinned OverPy 9.7.10 emission and the locale corpus, but the catalog treated it as an Abort alias and named Break 跳出循环. Make 中断 the Break spelling and keep 跳出循环 as a parse alias.

Use 正在使用辅助武器 as the Is Firing Secondary spelling, moving it off the isFiringSecondaryFire identity, and keep 正在发射辅助攻击 as a parse alias. Bastion compiled through Wright previously emitted 跳出循环 and 正在发射辅助攻击 where OverPy emits 中断 and 正在使用辅助武器.
@Teakowa
Teakowa merged commit 8da98ce into main Sep 25, 2026
5 checks passed
@Teakowa
Teakowa deleted the fix/zh-cn-break-firing-secondary branch September 25, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants