Fixes — Chinese and Cantonese in Local Inference
If you used Local Inference with Edge TTS or Bing Translator, picking Chinese or Cantonese as target was effectively broken. This release fixes three related bugs:
-
Chinese no longer speaks in Cantonese. With Edge TTS, "Chinese" silently defaulted to a Hong Kong Cantonese voice (
zh-HK-HiuGaaiNeural) because Microsoft's voice list returns Cantonese voices before Mandarin ones, and the auto-picker took the first result. Chinese now defaults to Mandarin (zh-CN). Cantonese remains available as its own target language. -
Cantonese no longer crashes the pipeline. Selecting Cantonese used to throw
Invalid language tag: cantoneseinside the TTS sentence splitter, dropping every translation. It now works end-to-end, with a fallback for any other unrecognized language tag. -
Bing Translator now accepts Cantonese. English → Cantonese via Bing was rejected as an unsupported code; it's now correctly mapped to Bing's
yueand works like any other language pair.
Voice picker clarity
Edge TTS voice names in Settings now include their locale suffix (e.g. Xiaoxiao (Female, zh-CN) vs Hiu Gaai (Female, zh-HK)) so you can tell Mandarin, Cantonese, and Taiwanese variants apart at a glance. If your saved Chinese voice was a Cantonese one from before this release, it will be auto-corrected to a Mandarin voice next time you open Local Inference.
Under the hood
- Bumped `@huggingface/transformers` to `^4.2.0` for the Qwen translation path.
Full Changelog: v0.21.0...v0.21.1