Skip to content

Non-English translations render escaped HTML as text and wrap bold headings in code blocks #43888

Closed

Description

@ff1451

Code of Conduct

What article on docs.github.com is affected?

The following pages are affected when viewed in any non-English language (e.g. Korean, Japanese, Spanish):

[english docs]
Image

[korean(not english) docs ]
Image

[english docs]
Image

[korean(not english) docs ]
Image

What changes are you suggesting?

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 &lt;code&gt;. 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:

  1. Unescape entity-encoded HTML tags (&lt;code&gt; → <code>) when the same tag appears as raw HTML in the English source.
  2. 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).

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Apr 20, 2026
  2. welcome commented on Apr 20, 2026

    @welcome

    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.

  3. added
    triageDo not begin working on this issue until triaged by the team
    on Apr 20, 2026
  4. added
    localizationIssue or PR relating to translation or localization
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Apr 20, 2026
  5. Sharra-writes commented on Apr 20, 2026

    @Sharra-writes
    Contributor

    @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.

  6. weeteckt commented on Apr 22, 2026

    @weeteckt

    Issue acknowledged by localization team and ported internally for follow-up

  7. github-actions commented on May 25, 2026

    @github-actions
    Contributor

    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.

  8. added
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on May 25, 2026
  9. removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Jun 5, 2026
  10. Sharra-writes commented on Jul 8, 2026

    @Sharra-writes
    Contributor

    @ff1451 Since the localization team has ported this issue over, we are going to close it here. 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamlocalizationIssue or PR relating to translation or localization

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions