YNYN Translation Workshop
2.2.7中文

YN quality checks

中文 · Project · Project examples

YN combines structural checks, independent AI review and editable line inspection. This page links the checks and their reproduction commands.

Check coverage

FailureReproducible sourceScope
Damaged placeholders, tags, control codes or row countsTranslation validator testsDeclared row and token structure
Proofreading suggestions breaking preservationReplacement validatorPhysical-line, placeholder and preservation checks at submission
Preserved text colliding with residue/terminology checksMatcher parity testsExclude actual preserved positions; still check prose
False untranslated findings blocking valid candidatesParent decisions · Native reviewExact row/text/reason decisions across formats; other structure remains enforced
Bibliography translated accidentallyReference workflow regressionHost-owned rows, existing HTML rebinding and original exported glyph pixels
PDF visual wraps fragmenting proseParagraph boundaries, Host/HTML/export regressionFirst/hanging indentation, narrow prose, native paragraph/table ownership, inline formulas and ordered flow areas
Academic PDF names, acronyms and numbering reported as untranslatedPrescan and native Pi regressionSource-evidenced row scopes shared by translation, review and import; prose still checked, without extra model requests
Interrupted drafts and stale scope/review proofRecovery preflight testsVerify old proof, retain unchanged rows and compensate failed commits
Omitted or rewritten PDF code/mathChild-write regression · PDF protection testsHost skeleton, prose-only writes, no translation requests for all-protected chunks
Exit after file replacement but before checkpointCold PDF recoveryIsolated process exits at the commit window; a new Host verifies its write-ahead receipt
Long history and shutdown persistenceStop/storage test · Session storageNative history retained; derived indexes do not replace proof
Large-candidate validation, import and cancellationResponsiveness test · Cancellation testBackground validation, cancellation and transactional commits

Reproduce

Use Node.js 22.19 or newer and the repository lock:

npm ci
npm test

Run the cold PDF recovery regression alone:

node --experimental-strip-types tests/pdf-protected-recovery.test.mjs

Desktop, LAN, API and package check commands are listed in development and validation. Dependency versions are defined by package.json and the lockfile.

Review and recovery

Structural checks inspect rows, control tokens, write scope and evidence bindings. Independent AI review checks meaning and terminology using source text and context. Split proofreading covers its assigned rows; Monte Carlo uses stratified samples. Findings are available in the review page for editing and acceptance.

Missing required files, internal errors and stalled repairs stop the task while retaining drafts and diagnostics. Recovery verifies the saved content and evidence before resuming. PDF input requirements and asset handling are described in the PDF guide.

Enlarged product screenshot