You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Non-English translations render escaped HTML as text and wrap bold headings in code blocks #43888
Two rendering bugs affect all non-English translations of GitHub Actions runner documentation.
Bug 1: Raw HTML tags visible in tables
In translated pages, inline HTML elements such as <code><a href="...">ubuntu-latest</a></code> inside table <td> cells are displayed as literal text (e.g. <code>ubuntu-latest</code>) instead of being rendered as styled code elements.
This happens because the translation pipeline (Crowdin) entity-encodes angle brackets, turning <code> into <code>. The translation correction pipeline in src/languages/lib/correct-translation-content.ts does not unescape these HTML entities.
Bug 2: Bold headings rendered inside code blocks
Between code blocks, bold heading lines (e.g. **Needed for downloading actions:**) are wrapped in bare code fences (```) by the translation pipeline, causing them to render as code blocks instead of formatted headings.
Proposed fix:
Both bugs can be corrected in src/languages/lib/correct-translation-content.ts:
Unescape entity-encoded HTML tags (<code> → <code>) when the same tag appears as raw HTML in the English source.
Strip bare code-fence wrapping from lines that contain only a bold heading (**...**).
Additional information
Affected languages: All non-English translations (confirmed in Korean /ko).
Root cause: Crowdin translation pipeline corrupts inline HTML and markdown structure.
Browser: Reproducible in any browser (not a client-side issue).
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
@ff1451 I'm pretty sure I can submit this as a coherent but report. I've already marked it for that team, so hopefully they see it, but if they don't get to it by the time I have five or six localization issues, I'll just submit them all as bug reports and then close them here.
A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.
Activity
welcome commentedon Apr 20, 2026
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Sharra-writes commentedon Apr 20, 2026
@ff1451 I'm pretty sure I can submit this as a coherent but report. I've already marked it for that team, so hopefully they see it, but if they don't get to it by the time I have five or six localization issues, I'll just submit them all as bug reports and then close them here.
weeteckt commentedon Apr 22, 2026
Issue acknowledged by localization team and ported internally for follow-up
github-actions commentedon May 25, 2026
A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.
Sharra-writes commentedon Jul 8, 2026
@ff1451 Since the localization team has ported this issue over, we are going to close it here. 💛