[PR #14219] [MERGED] Fix: Solve equation problems with Chinese symbols #10211

New Issue

GiteaMirror · 2025-11-11T18:59:07-06:00

GiteaMirror commented

2025-11-11 18:59:07 -06:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14219
Author: @Yu-QX
Created: 5/23/2025
Status: ✅ Merged
Merged: 5/23/2025
Merged by: @tjbck

Base: dev ← Head: main

📝 Commits (1)

ec97fdf Fix: Solve equation problems with Chinese symbols by adding more symbols to the ALLOWED_SURROUNDING_CHARS

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 src/lib/utils/marked/katex-extension.ts (+2 -1)

📄 Description

Explanations to Changes

This change added more symbols to ALLOWED_SURROUNDING_CHARS in the markdown extension, so that the rendering problem of equations in non-English context is solved.

Example problems:

Next Steps

More changes should be made to the markdown extension, to tackle problems with bold and italic. We are also open to more formatting problems, especially with non-English context.

See more in Wiki.

Thank you!

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/14219 **Author:** [@Yu-QX](https://github.com/Yu-QX) **Created:** 5/23/2025 **Status:** ✅ Merged **Merged:** 5/23/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `main` --- ### 📝 Commits (1) - [`ec97fdf`](https://github.com/open-webui/open-webui/commit/ec97fdf5d669928277c9b01a7b7f93b379d44607) Fix: Solve equation problems with Chinese symbols by adding more symbols to the ALLOWED_SURROUNDING_CHARS ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/utils/marked/katex-extension.ts` (+2 -1) </details> ### 📄 Description ## Explanations to Changes This change added more symbols to `ALLOWED_SURROUNDING_CHARS` in the markdown extension, so that the rendering problem of equations in non-English context is solved. > Example problems: <img width="491" alt="Screenshot 2025-05-22 223854" src="https://github.com/user-attachments/assets/bf48239c-ea30-4e77-9836-3e9dd591de98" /> <img width="683" alt="Screenshot 2025-05-22 223956" src="https://github.com/user-attachments/assets/92fc7b8a-116a-4332-926d-af0df72e6bcf" /> ## Next Steps More changes should be made to the markdown extension, to tackle problems with **bold** and *italic*. We are also open to more formatting problems, especially with non-English context. See more in [Wiki](https://github.com/Yu-QX/open-webui-DIS-14085/wiki). Thank you! --- # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-11 18:59:07 -06:00

GiteaMirror closed this issue

2025-11-11 18:59:07 -06:00

GiteaMirror referenced this issue

2026-04-19 21:55:35 -05:00

[GH-ISSUE #10211] Unable to edit knowledge uploaded file #15809

GiteaMirror referenced this issue

2026-04-25 05:19:14 -05:00

[GH-ISSUE #10211] Unable to edit knowledge uploaded file #31338

GiteaMirror referenced this issue

2026-05-05 16:17:38 -05:00

[GH-ISSUE #10211] Unable to edit knowledge uploaded file #54475