AllTalk TTS: Czech diacritics lost (non-UTF8 form encoding in request)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start at the AllTalk TTS integration and trace the POST request sent to /api/tts-generate, comparing its form-body encoding and Content-Type with the working PowerShell request. Reproduce with the Czech sample text and verify that AllTalk receives and preserves ř, č, ž, and other diacritics.
Written by the indexing model from the issue text.
Description
Subtitle Edit version: [Subtitle Edit 4.0.14]
Windows: [doplň verzi - např. Windows 10 22H2]
AllTalk: [v1.9c] running on http://127.0.0.1:7851
TTS Engine: AllTalk TTS (Coqui XTTSv2 based)
Language: Czech (cs)
Problem
When generating TTS via AllTalk from Subtitle Edit, Czech diacritics (ř, č, ž, etc.) are corrupted.
Example input in Subtitle Edit:
Takže čeština tu funguje suprově, co ty tomu říkáš?
What AllTalk receives (visible in console log):
Take etina tu funguje suprov, co ty tomu íká?
However, AllTalk itself handles Czech correctly when called directly via API.
Evidence / Reproduction
Calling AllTalk API directly via PowerShell works correctly and preserves diacritics:
$body = @{
text_input = "Takže čeština tu funguje suprově, co ty tomu říkáš?"
text_filtering = "none"
character_voice_gen = "female_01.wav"
narrator_enabled = "false"
narrator_voice_gen = "male_01.wav"
text_not_inside = "character"
language = "cs"
output_file_name = "ps_test"
output_file_timestamp= "true"
autoplay = "false"
autoplay_volume = "0.8"
}
Invoke-RestMethod -Method Post `
-Uri "http://127.0.0.1:7851/api/tts-generate" `
-ContentType "application/x-www-form-urlencoded; charset=utf-8" `
-Body $body
...
AllTalk console output (correct):
[AllTalk TTSGen] Takže čeština tu funguje suprově, co ty tomu říkáš?
Root Cause (suspected)
Subtitle Edit likely encodes the POST request body using the system codepage
(Encoding.Default / CP-1250) instead of UTF-8 when sending
application/x-www-form-urlencoded data, causing non-ASCII characters
to be corrupted before reaching AllTalk.
Suggested Fix
Ensure UTF-8 encoding is used for application/x-www-form-urlencoded POST bodies
and explicitly set Content-Type: application/x-www-form-urlencoded; charset=utf-8
in the HTTP request headers.
Related
Similar encoding issues have been reported in:
- #3384
- #8686
- Dominant language
- C#
- Stars
- 14.3k
- Forks
- 1.3k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 782
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SubtitleEdit/subtitleedit
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#14950 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SubtitleEdit/subtitleedit#14726 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SubtitleEdit/subtitleedit#14510 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#12576 ·
All issues in SubtitleEdit/subtitleedit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·