From: Jarek C. <jar...@po...> - 2013-08-30 08:53:38
|
Hi Joseph W dniu 2013-08-30 10:24, Joseph Lee pisze: > Hi, > A few things to consider: > 1. Content language switching requires that a webpage or the content > expose relevant language code marker to tell NVDA to switch a > synthesizer's speech language to a particular language. This was met > with mixed success - in some cases, webpages and contents does not > include such a marker. I mean manual switching of content language. In next stage this could be switchable on application basis, but I think the manual switching of the content language would be most frequent operation. The only one operation to do, the rest (interface and nvda language) would stay constant and the whole thing should work smoothly. > 2. You can in fact switch NVDA's languages already - from General > Settings, one can indeed use English interface instead of using > Windows locale language. Yes, but when I switch nvda language it is being spoken in a different language, the one that is in voice settings. But you are right. We already have this setting, there is no need to introduce a new one for nvda language. Thanks for your remarks Jarek |