[ x] I have read and followed all the instructions provided in the README.md.
[x ] I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Description:
The Text-to-Speech (TTS) feature has an issue when converting Markdown text to audio. It reads specific Markdown syntax, such as ### for headings, instead of ignoring these markers and focusing only on the textual content. This results in an unnatural and inconsistent user experience.
Steps to Reproduce:
Provide a Markdown-formatted text to the TTS feature, for example:
### Example Heading
Here is a paragraph.
Trigger the audio conversion.
Listen to the output.
Current Result:
The TTS reads:
"Hashtag hashtag hashtag Example Heading Here is a paragraph."
Expected Result:
The TTS should ignore Markdown syntax and read only the textual content:
"Example Heading. Here is a paragraph."
Impact:
This bug affects the clarity of audio conversion, making it less practical for professional or educational use.
Proposed Fix:
Implement a pre-processing step that:
Strips or ignores Markdown syntax from the input text before passing it to the TTS engine.
Ensures Markdown styling does not interfere with the readability of the content.
Labels: bug, text-to-speech, markdown
Originally created by @flefevre on GitHub (Nov 20, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7125
# Bug Report
## Installation Method
docker 0.4.1
## Environment
- **Open WebUI Version:** [e.g., v0.3.11]
- **Ollama (if applicable):** [e.g., v0.2.0, v0.1.32-rc1]
**Confirmation:**
- [ x] I have read and followed all the instructions provided in the README.md.
- [x ] I am on the latest version of both Open WebUI and Ollama.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
- [ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Description:
The Text-to-Speech (TTS) feature has an issue when converting Markdown text to audio. It reads specific Markdown syntax, such as ### for headings, instead of ignoring these markers and focusing only on the textual content. This results in an unnatural and inconsistent user experience.
**Steps to Reproduce**:
1. Provide a Markdown-formatted text to the TTS feature, for example:
```markdown
### Example Heading
Here is a paragraph.
```
2. Trigger the audio conversion.
3. Listen to the output.
**Current Result**:
The TTS reads:
> "Hashtag hashtag hashtag Example Heading Here is a paragraph."
**Expected Result**:
The TTS should ignore Markdown syntax and read only the textual content:
> "Example Heading. Here is a paragraph."
**Impact**:
This bug affects the clarity of audio conversion, making it less practical for professional or educational use.
**Proposed Fix**:
Implement a pre-processing step that:
1. Strips or ignores Markdown syntax from the input text before passing it to the TTS engine.
2. Ensures Markdown styling does not interfere with the readability of the content.
**Labels**: `bug`, `text-to-speech`, `markdown`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @flefevre on GitHub (Nov 20, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7125
Bug Report
Installation Method
docker 0.4.1
Environment
Confirmation:
Description:
The Text-to-Speech (TTS) feature has an issue when converting Markdown text to audio. It reads specific Markdown syntax, such as ### for headings, instead of ignoring these markers and focusing only on the textual content. This results in an unnatural and inconsistent user experience.
Steps to Reproduce:
Current Result:
The TTS reads:
Expected Result:
The TTS should ignore Markdown syntax and read only the textual content:
Impact:
This bug affects the clarity of audio conversion, making it less practical for professional or educational use.
Proposed Fix:
Implement a pre-processing step that:
Labels:
bug,text-to-speech,markdown@flefevre commented on GitHub (Nov 20, 2024):
error