Core: Preserve Markdown URLs during translation - #509
Draft
Minseok Song (skytin1004) wants to merge 1 commit into
Draft
Core: Preserve Markdown URLs during translation#509Minseok Song (skytin1004) wants to merge 1 commit into
Minseok Song (skytin1004) wants to merge 1 commit into
Conversation
Minseok Song (skytin1004)
force-pushed
the
fix/markdown-url-preservation
branch
from
August 9, 2026 10:48
3663475 to
ed7d6ed
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Prevent translation providers and path rewriting from modifying URLs in Markdown links and images.
Description
Markdown link destinations were sent directly to the translation model. Although the prompt instructed the model to preserve URLs, a live translation changed
WT.mc_idtoWT_mc_idin several links.This change:
Internal
#anchordestinations remain visible so they can still be aligned with translated heading slugs.Related Issue
Follow-up to #508.
Does this introduce a breaking change?
Will this change require users to update commands, configuration, environment variables, generated translation output, or public Python/MCP APIs?
If you're not sure, test the affected CLI, API, documentation, or GitHub Actions workflow before marking this as "No."
Type of change
Checklist
Before submitting your pull request, please confirm the following:
Additional context
All 332 non-API tests pass, and Ruff and Black checks pass. I also verified the affected
generative-ai-for-beginnersREADME with a live Azure OpenAI translation: all 121 external URLs and all 105WT.mc_idparameters were preserved, with no modified URLs or unresolved placeholders.