Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown display is broken with latex markers being improperly interpreted #410

Open
phazei opened this issue Feb 6, 2025 · 2 comments
Open

Comments

@phazei
Copy link

phazei commented Feb 6, 2025

Which version of LM Studio?
LM Studio 0.3.9

Which operating system?
Windows 11

Image
Image

I should be able to use normal text characters even if it's markdown, I've never seen a markdown viewer break with dollar signs and percent characters.

@MovGP0
Copy link

MovGP0 commented Feb 8, 2025

Text bewteen $ characters is interpreted as LaTeX code and therefore rendered as mathematical formula using MathJax. This is how a markdown viewer should behave.

So from my perspective, this is the correct behavior.

@phazei
Copy link
Author

phazei commented Feb 10, 2025

So you're saying that anytime someone turns on MarkDown, now dollar signs can't be used without explicit escaping? Well, that's not how a single LLM markdown viewer works.

Now, on any model I use, anytime I discuss money, both my input text and their output text gets messed up and is missing things for formatted poorly.

WIth deepseek, chatgpt, claude, all of them support latex, and markdown, and have no issues displaying $1.23 from input or output.

Image

I also tried a whole bunch of combinations in Claude with no issues.

It seems that once the latex section is open, then I use a % sign, which starts a latex comment and while it displays without italics, breaks the rest of the markdown. But with most interpreters, I think there are additional checks to make sure the casual use of a $ doesn't initiate latex.

@phazei phazei changed the title Markdown display is broken Markdown display is broken with latex markers being improperly interpreted Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants