fix(ro): remove latex from headings in chapter12/3a #1122
Merged
Conversation
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
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this PR do?
Fixes the build failure in Romanian translation caused by LaTeX expressions in Markdown headings.
Closes #1121
Why these changes?
The MDX processor converts LaTeX in headings to HTML with
{@html}tags, which Svelte doesn't allow in component attribute values. This was causing build failures for all PRs, not just Romanian translation PRs.Testing
Additional Context
This issue was discovered while working on Korean translation PR #1095. The build was failing due to this pre-existing issue in the Romanian files, affecting all PRs that trigger documentation builds.
@stevhliu May you please review this PR? 🤗