[FEATURE][WINDOWS]Context-aware capitalization, trailing punctuation, and preferred language setting
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
The issue does not name files or tests. First locate the Windows dictation text-insertion flow and the Voice Engine settings, then trace how the Blazing fast engine handles language selection. The requested work is complete when capitalization and trailing punctuation follow the surrounding text, and users can set a preferred dictation language for that engine.
Written by the indexing model from the issue text.
Description
Problem
Here are the two problems:
-
Incorrect capitalization and punctuation when inserting text mid-sentence
When dictating a passage into an existing sentence, FluidVoice usually capitalizes the first letter of the inserted text and adds a period at the end. These things have to be corrected manually every time when inserting text mid-sentence. -
No preferred language setting
Without a way to set a preferred dictation language, the model has to guess the language for every short phrase (especially 2–3 word utterances). This frequently leads to incorrect transcriptions.
Proposed solution
Feature Request
I’m using FluidVoice 0.0.9 on Windows and it's really great! Though would suggest the following improvements for the real-time dictation:
1. Capitalization rules
Before inserting dictated text, check the character immediately before the cursor, ignoring all consecutive spaces.
Example: if the text before the cursor is "кгаож ", treat "ж" as the previous character.
- Then capitalize the first letter only if the previous relevant character is a period (
.) or a newline. If the previous character is a period or newline, the first letter must be uppercase. - In all other cases, start with a lowercase letter. It'd be very useful when trying to insert a few additional words in an existing sentence.
2. Trailing punctuation rules
Also check the character immediately after the cursor (again ignoring consecutive spaces).
Example: if the text after the cursor is " врата", consider only "в".
- Then if the next relevant character is not uppercase, the dictated text should not end with sentence-ending punctuation (
.,?, or!) but with a pause. - Otherwise, if the next relevant character **is ** uppercase one has to end with sentence-ending punctuation (
.,?, or!).
3. Preferred language setting
Please add a setting for the preferred dictation language (e.g. German, French, Bulgarian) in Blazing fast engine (now it works only in Nemotron). The onboarding says "You can change this later in Voice Engine settings" yet I can't see such a setting.
By adding the preferred dictation language one should improve the recognition accuracy, especially for short phrases of one or two words, by preventing the model from guessing the language every time.
Thank you!
P.S.
I just have to say you did really amazing work on FluidVoice. It’s the best voice-to-text software I’ve used so far.
Alternatives considered
No response
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 altic-dev/FluidVoice
-
[BUG] File transcription skips audio chunks shorter than one secondPossibly taken @sabbah13 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1161 ·
Maintainers usually reply within 1 day
-
[BUG]Openbug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
altic-dev/FluidVoice#1171 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
altic-dev/FluidVoice#1170 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
altic-dev/FluidVoice#1169 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
altic-dev/FluidVoice#1168 · 2 comments ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
type: cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/google-cloud-swift#1477 ·
Maintainers usually reply within 1 day
-
product / auth product / console product / databases product / messaging product / self-hosted product / sites product / storage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
P1 status: first-line-handled status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
a2ui-project/a2ui#3282 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
element-hq/element-x-ios#6357 ·
Maintainers usually reply within 1 day