Clarify Reson8 language fallback docs#85
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughReson8 add-on documentation is updated in both German and English versions to clarify language selection behavior. The Features section and Transcription mode table now consistently describe that a single language is passed to Reson8, with first-supported-language fallback when multiple languages are selected and auto-detection when none are selected. ChangesReson8 Language Handling Documentation Clarification
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
Summary
Issue context
This is a website documentation follow-up for TypeWhisper/typewhisper-mac#627 and the Reson8 capability correction in TypeWhisper/typewhisper-mac#639. The live Reson8 page still said multiple language hints fall back to unrestricted Reson8 auto-detect, which is no longer accurate for the fixed macOS behavior.
References TypeWhisper/typewhisper-mac#627.
References TypeWhisper/typewhisper-mac#639.
Test plan
npm run test:i18nnpm run buildSummary by CodeRabbit