[GH-ISSUE #3798] [Docs] Correct misleading Korean website translations #1473

New issue

Closed

opened 2026-10-16 21:05:48 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-16 21:05:48 +00:00

Owner

Originally created by @hi2242 on GitHub (Oct 15, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3798

Before submitting

I searched the existing issues for a related documentation report.
I removed credentials, tokens, private paths, and sensitive target data.

Documentation location

Korean website catalog, particularly the reconstruction essays, analysis guides, case studies, and figure/runtime labels.

Problem

Several Korean translations change the technical meaning or omit essential terms, making the instructions and examples difficult to follow. Examples found by comparing msgid with msgstr:

Git becomes 자식 (child) in “Use the repository and Git as working memory.”
“Read the C++” becomes 읽기 C++, while “Assembly to C++” loses C++ entirely.
“Read the CTF case study” becomes 공정거래위원회 사례 연구 읽기 (Fair Trade Commission case study).
“IPC” becomes 2015 년 (year 2015).

Spacing, awkward sentence order, and periods at the end of Korean headings also reduce readability. This affects readers using the Korean website edition.

Expected content

Use natural Korean with consistent reverse-engineering terminology, guided by the English source and translation instructions. Preserve code, commands, product names, numerical evidence, placeholders, and provenance. Keep roughly comparable text length; remove trailing periods from Korean headings while retaining sentence punctuation in prose.

Supporting evidence

The examples above are source-derived findings from the pinned catalog, not a runtime-provider diagnosis. A local correction was rendered and served over HTTP; the Korean homepage, setup guide, reconstruction essay, and TH04 case study returned HTTP 200. Strict catalog validation passed: 1728/1728 translated; 0 missing or fuzzy.

Additional context

The proposed correction changes only website/locales/ko/messages.po. Local prerequisites have now been prepared: pinned Node 24.18.0/npm 11.16.0 with locked npm dependencies, native Cairo 1.18.6/CairoSVG 2.9.1, and DejaVu Sans 2.37. Child Python processes use PYTHONUTF8=1 on Windows.

Final-head verification at 8ab17051a3bdfca2298b2478c52ffcdd98333253: passed: 380 reading pages built in 20 languages; social-card.png generated at 1200 × 630; 382 HTML pages, 26,087 local references, SVG/ZIP assets, sharing/search metadata and sitemap verified; all 16 regression tests passed. npm run check, npm run check:fast, strict Korean catalog validation (1,728/1,728), and the catalog preservation comparison also passed. The prior missing-Cairo/missing-PNG limitation is resolved. No interactive visual/browser or real-provider verification is claimed; full validation details are in #3799.

Originally created by @hi2242 on GitHub (Oct 15, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3798 ### Before submitting - [x] I searched the existing issues for a related documentation report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Documentation location [Korean website catalog](https://github.com/morluto/rea/blob/d69acc3455c33f90a2fc4381db43d38b6af50622/website/locales/ko/messages.po), particularly the reconstruction essays, analysis guides, case studies, and figure/runtime labels. ### Problem Several Korean translations change the technical meaning or omit essential terms, making the instructions and examples difficult to follow. Examples found by comparing `msgid` with `msgstr`: - Git becomes `자식` (child) in “Use the repository and Git as working memory.” - “Read the C++” becomes `읽기 C++`, while “Assembly to C++” loses C++ entirely. - “Read the CTF case study” becomes `공정거래위원회 사례 연구 읽기` (Fair Trade Commission case study). - “IPC” becomes `2015 년` (year 2015). Spacing, awkward sentence order, and periods at the end of Korean headings also reduce readability. This affects readers using the Korean website edition. ### Expected content Use natural Korean with consistent reverse-engineering terminology, guided by the English source and [translation instructions](https://github.com/morluto/rea/blob/d69acc3455c33f90a2fc4381db43d38b6af50622/website/locales/README.md). Preserve code, commands, product names, numerical evidence, placeholders, and provenance. Keep roughly comparable text length; remove trailing periods from Korean headings while retaining sentence punctuation in prose. ### Supporting evidence The examples above are source-derived findings from the pinned catalog, not a runtime-provider diagnosis. A local correction was rendered and served over HTTP; the Korean homepage, setup guide, reconstruction essay, and TH04 case study returned HTTP 200. Strict catalog validation passed: `1728/1728 translated; 0 missing or fuzzy`. ### Additional context The proposed correction changes only `website/locales/ko/messages.po`. Local prerequisites have now been prepared: pinned Node 24.18.0/npm 11.16.0 with locked npm dependencies, native Cairo 1.18.6/CairoSVG 2.9.1, and DejaVu Sans 2.37. Child Python processes use `PYTHONUTF8=1` on Windows. Final-head verification at `8ab17051a3bdfca2298b2478c52ffcdd98333253`: passed: 380 reading pages built in 20 languages; `social-card.png` generated at 1200 × 630; 382 HTML pages, 26,087 local references, SVG/ZIP assets, sharing/search metadata and sitemap verified; all 16 regression tests passed. `npm run check`, `npm run check:fast`, strict Korean catalog validation (1,728/1,728), and the catalog preservation comparison also passed. The prior missing-Cairo/missing-PNG limitation is resolved. No interactive visual/browser or real-provider verification is claimed; full validation details are in #3799.

bsakaguchi commented

2026-10-16 21:05:49 +00:00

Author

Owner

@XinwangTao commented on GitHub (Oct 15, 2026):

The example mistakes are convincing — translating Git as 자식, dropping C++ from "Assembly to C++", and rendering IPC as a year are exactly the kind of errors that make technical documentation unusable for readers who cannot fall back on the English original. Keeping code, product names and provenance untranslated is the right policy, and removing trailing periods from Korean headings is a good consistency rule. The 1728/1728 catalog validation gives confidence the change is complete rather than partial; the only gap (missing Cairo library) is clearly scoped and does not affect the translation itself.

@XinwangTao commented on GitHub (Oct 15, 2026): The example mistakes are convincing — translating Git as 자식, dropping C++ from "Assembly to C++", and rendering IPC as a year are exactly the kind of errors that make technical documentation unusable for readers who cannot fall back on the English original. Keeping code, product names and provenance untranslated is the right policy, and removing trailing periods from Korean headings is a good consistency rule. The 1728/1728 catalog validation gives confidence the change is complete rather than partial; the only gap (missing Cairo library) is clearly scoped and does not affect the translation itself.

bsakaguchi commented

2026-10-16 21:05:50 +00:00

Author

Owner

@hi2242 commented on GitHub (Oct 15, 2026):

@XinwangTao Thank you for reading the report so carefully and for the thoughtful feedback. I appreciate you checking both the translation examples and the validation scope — your comments help make the report clearer and more useful.

@hi2242 commented on GitHub (Oct 15, 2026): @XinwangTao Thank you for reading the report so carefully and for the thoughtful feedback. I appreciate you checking both the translation examples and the validation scope — your comments help make the report clearer and more useful.

bsakaguchi closed this issue

2026-10-17 21:02:01 +00:00

bsakaguchi referenced this issue

2026-10-17 21:11:44 +00:00

[PR #1473] [MERGED] perf(artifacts): deliver the inspected artifact graph once #2911