Skip to content

Non-English translations break Markdown links containing Liquid variables #43996

Description

@Coin-233

Code of Conduct

What article on docs.github.com is affected?

Multiple non-English localized articles, including but not limited to:

What changes are you suggesting?

The automated localization pipeline needs to be fixed so it doesn't break Markdown syntax when handling Liquid variables.

Additional information

The Issue:
In the localized versions (e.g., Chinese, Japanese, French), Markdown links that contain Liquid variables in the text part are failing to render. Instead of rendering as clickable hyperlinks, they are displayed as raw Markdown syntax, often wrapped in a plain text code block.

Example from source:
* [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)

Actual Behavior (in localized docs):
It renders exactly as [GitHub Flavored Markdown の仕様](https://github.github.com/gfm/) or [Spécification Flavored Markdown GitHub](https://github.github.com/gfm/) in plain text.

Expected Behavior:
It should render as a standard, clickable HTML <a> link.

Additional information

#43888 #43870

Screenshots:

Image Image Image Image Image

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Apr 27, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Apr 27, 2026
  3. Sharra-writes commented on Apr 27, 2026

    @Sharra-writes
    Contributor

    Thanks for reaching out and flagging this! Since we use an internal, automated solution for our translated docs, I will flag your request for our team 💛

    For more information on translations, please see this page ✨

  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 27, 2026
  5. weeteckt commented on Apr 29, 2026

    @weeteckt

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

  6. JiMI-Ha commented on May 2, 2026

    @JiMI-Ha
  7. github-actions commented on Jun 22, 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 Jun 22, 2026
  9. Coin-233 commented on Jun 22, 2026

    @Coin-233
    Author

    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.

    nope

  10. removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Jun 29, 2026
  11. Sharra-writes commented on Jul 8, 2026

    @Sharra-writes
    Contributor

    @Coin-233 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