fix(ui): render LaTeX-style inline math commands in chat markdown#5
Merged
Conversation
Some models emit `$\rightarrow$` and similar LaTeX commands that marked does not render. Substitute the common ones with their Unicode equivalent before parsing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Translate common LaTeX inline-math commands (
$\rightarrow$,$\times$,$\leq$, …) to Unicode glyphs beforemarked.parse, so model output that uses LaTeX renders correctly instead of showing literal$\rightarrow$.Why: LLMs frequently emit LaTeX-style notation for arrows and math symbols, which marked passes through verbatim — visible as raw
$\command$in chat.Regression risks:
$\command$occurrences inside fenced code blocks and inline backticks. Acceptable for chat content, but if users paste LaTeX into a code sample it will be mangled. Move the substitution into a marked renderer hook if that becomes a problem.$\foo$), so no silent data loss.