[PR #14308] [CLOSED] fix: Handle special cases of LLM output not following markdown syntax #62294

New Issue

GiteaMirror · 2026-05-06T06:22:23-05:00

GiteaMirror commented

2026-05-06 06:22:23 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14308
Author: @Yu-QX
Created: 5/25/2025
Status: ❌ Closed

Base: dev ← Head: main

📝 Commits (1)

49fe137 fix: Handle special cases of LLM output not following markdown syntax 20250525

📊 Changes

2 files changed (+87 additions, -0 deletions)

View changed files

📝 src/lib/utils/index.ts (+6 -0)
➕ src/lib/utils/processResponseContent/special-cases.ts (+81 -0)

📄 Description

fix: Handle special cases of LLM output not following markdown syntax

The $2^{\text{nd}}$ change basing on Discussion #14085.

Modified on 2025-05-25.

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

This pull request introduces a new utility function specialCases to handle special cases of LLM output that do not follow markdown syntax, particularly focusing on Chinese characters and parentheses. The function ensures that the original text is modified as little as possible while addressing specific rendering issues.

Added

Added a new file $lib/utils/processResponseContent/specialCases.ts to handle special cases of LLM output.
Added a new folder $lib/utils/processResponseContent/ to organize utility functions for processing response content.

Changed

Updated the processResponseContent function in $lib/utils/index.ts to include the new specialCases function.

Fixed

Fixed an issue where Chinese parentheses inside bold or italic text caused markdown parsing to fail. The solution involves adding spaces around the bold or italic text to ensure proper rendering.

Additional Information

The changes are focused on improving the rendering of LLM output, particularly for non-English characters. Future issues can be addressed by adding new utility functions to the $lib/utils/processResponseContent/ folder.
The function specialCases is designed to handle specific cases and should not be used for general markdown parsing issues.

Screenshots or Videos

The changes are visual, and the screenshots demonstrate the improvement in rendering.
Before the changes:

After 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/14308 **Author:** [@Yu-QX](https://github.com/Yu-QX) **Created:** 5/25/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `main` --- ### 📝 Commits (1) - [`49fe137`](https://github.com/open-webui/open-webui/commit/49fe137553c6a47be388fac9e6e5e89fd95aee26) fix: Handle special cases of LLM output not following markdown syntax 20250525 ### 📊 Changes **2 files changed** (+87 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/utils/index.ts` (+6 -0) ➕ `src/lib/utils/processResponseContent/special-cases.ts` (+81 -0) </details> ### 📄 Description # fix: Handle special cases of LLM output not following markdown syntax The **$2^{\text{nd}}$** change basing on [Discussion #14085](https://github.com/open-webui/open-webui/discussions/14085). > Modified on 2025-05-25. **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. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **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 - This pull request introduces a new utility function `specialCases` to handle special cases of LLM output that do not follow markdown syntax, particularly focusing on Chinese characters and parentheses. The function ensures that the original text is modified as little as possible while addressing specific rendering issues. ### Added - Added a new file `$lib/utils/processResponseContent/specialCases.ts` to handle special cases of LLM output. - Added a new folder `$lib/utils/processResponseContent/` to organize utility functions for processing response content. ### Changed - Updated the `processResponseContent` function in `$lib/utils/index.ts` to include the new `specialCases` function. ### Fixed - Fixed an issue where Chinese parentheses inside bold or italic text caused markdown parsing to fail. The solution involves adding spaces around the bold or italic text to ensure proper rendering. --- ### Additional Information - The changes are focused on improving the rendering of LLM output, particularly for non-English characters. Future issues can be addressed by adding new utility functions to the `$lib/utils/processResponseContent/` folder. - The function `specialCases` is designed to handle specific cases and should not be used for general markdown parsing issues. ### Screenshots or Videos - The changes are visual, and the screenshots demonstrate the improvement in rendering. - Before the changes: <img width="704" alt="Screenshot 2025-05-25 132035" src="https://github.com/user-attachments/assets/d6be3993-4caf-43ff-8692-2264520b7b18" /> - After the changes: <img width="693" alt="Screenshot 2025-05-25 131923" src="https://github.com/user-attachments/assets/2541c8cb-9c94-4b8c-819b-fc10ffb2f06b" /> ### 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 2026-05-06 06:22:23 -05:00

GiteaMirror closed this issue

2026-05-06 06:22:24 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#62294