mirror of
https://github.com/open-webui/open-webui.git
synced 2026-11-14 05:02:01 -06:00
[GH-ISSUE #14067] issue: Issues related to Markdown rendering of non-English chat content #17129
Reference in New Issue
Block a user
Originally created by @Yu-QX on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14067
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.6.5
Ollama Version (if applicable)
No response
Operating System
Windows 11
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Render different language properly.
Actual Behavior
When rendering chat content that includes Chinese, the application exhibits a noticeable anomaly, leading to the following phenomena:
\(……\)formulas, if there are no English punctuation marks before or after, the display is abnormal. This issue commonly occurs with Chinese parentheses(\(……\))and Chinese enumeration commas\(……\)、\(……\), while periods and commas do not have similar problems.**……**bold formatting, encountering Chinese punctuation causes anomalies. This issue commonly arises in structures like**中文名称(English name)**中文内容 (directly followed by Chinese text).Only common issues are reported here; the actual affected content may be more extensive. Testing shows that these rendering issues can be resolved by inserting an English space in the affected parts.
Since I frequently use this application as a note-taking tool, I hope to resolve display issues for all historical chat records. Rendering preprocessing is one solution. Before rendering, run the following code:
This solution has been effective in all tested cases.
Steps to Reproduce
You can also just type and send something like:
The following two pictures are among the cases.
Logs & Screenshots
Additional Information
Although I'm not using the latest version, the issue seems to persist in the later versions since I haven't read about any changes in the rendering process. And the problem has been there since I installed the app last year. I used to correct it by hand.
Meanwhile, I am aware that adding a function will help. But that is only addressing the symptoms without tackling the underlying issue.
@Yu-QX commented on GitHub (May 20, 2025):
Oh, the code should be further modified to prevent further strange behaviors. It currently doesn't consider something like unclosed symbols.
@tjbck commented on GitHub (May 20, 2025):
Model output issue not following the standard Markdown/LaTeX format, with that being said, PR welcome here.