New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The letter and punctuation names remain in the NVDA language even when the synthetizer is configured differently #4210
Comments
Comment 1 by jteh on 2014-06-20 10:04 |
Comment 2 by kredh on 2014-06-20 10:11 |
Comment 3 by jteh on 2014-06-20 11:05 |
Comment 4 by kredh on 2014-06-20 11:32 |
Comment 5 by jteh on 2014-06-20 11:54 I understand that you choose to switch synths yourself. However, this doesn't explain why having this option enabled is a problem for you. If you're going to switch anyway, the automatic switch might be wasted, but shouldn't be problematic. Can you explain the problems this causes for you? |
Comment 6 by kredh on 2014-06-20 12:09
I'm not asking that it be fixed, I can imagine how hard this feature (automatic language switching) is to implement in the first place. But the symbol names could still be in the synthetizer language without it enabled, I think, if the synthetizer is explicit about the language it uses currently. |
Comment 7 by jteh (in reply to comment 6) on 2014-06-20 12:29
If you're browsing an English site, I'm guessing you have to switch to Vocalizer manually anyway. Therefore, I don't follow why Eloquence switching to English is problematic, since you have to override it either way. What am I missing here?
NVDA currently only switches languages if the document explicitly specifies the language for a given piece of text. It's odd that the author intended this, even though you note this is not ideal.
It can't for several reasons:
If this does indeed need to be configurable, we'd need to introduce another option. I'm very reluctant to do this because this will be confusing for users and describing it is extremely difficult. This is why I want to make sure we fully understand your use case. |
Comment 8 by kredh on 2014-06-20 12:46 Anyway, I think it's a rather individual need and won't benefit much for the community itself, considering the time that would be necessary to fix it. So I think you can close this ticket. |
Comment 9 by jteh on 2014-12-02 06:06 |
Comment 10 by Michael Curran <mick@... on 2014-12-16 03:50
Changes:
|
Comment 11 by vgjh2005 on 2014-12-16 12:32 |
Comment 12 by jteh on 2014-12-16 12:38 |
Comment 13 by vgjh2005 on 2014-12-16 17:55 |
Comment 14 by jteh on 2014-12-16 23:25 |
Comment 15 by Michael Curran <mick@... on 2015-01-04 23:38
Changes:
|
Comment 16 by mdcurran on 2015-01-04 23:39 |
Comment 18 by leonarddr on 2015-02-16 21:36 |
Comment 19 by jteh on 2015-02-18 03:55 |
Hi, |
That suggests the voice reports it is zh_CN instead of zh_TW, which suggests a bug in the voice. |
Reported by kredh on 2014-06-20 09:58
The letter and punctuation names (spoken by NVDA synthetizer) are not in the synthetizer language, but remain in the NVDA language. My NVDA language is French, for instance, but when I activate a profile that uses a different synthetizer in English, the letter and punctuation names remain in French (. will be prununced point, not period or dot, for instance).
Blocking #3545
The text was updated successfully, but these errors were encountered: