I wanna programmatically set a TextBlock flow direction depended on user current writing landuage(NOT phone language). for example if keyboard is set to Arabic, RightToLeft and for English, LeftToRight. Is there anyway to get current keyboard language in windows phone 8 ???
That's a darn good question.
It doesn't seem to be exposed in Windows Phone 8.
I found this here Font and language configuration support for Windows Phone
Text input
The selection of languages for which a phone has preinstalled keyboards and input
method UIs is dependent on which market a phone is sold in. At any time the user
can download and use a keyboard for any of the 50 supported phone client UI
languages. The language of the keyboard, which determines the characters that
are written to a TextBox control, is not programmatically available to an app.
It's interesting to note that this IS available for Windows Store Apps.
See Windows.Globalization.Language.currentInputMethodLanguageTag.
Oh Microsoft...
Related
What is needed in order to make the InputScope effective for Windows IoT Core development in order to limit the On-Screen Keyboard layout? I know from the following article that:
"This info applies only to the SIP. It does not apply to hardware
keyboards or the On-Screen Keyboard available in the Windows Ease of
Access options."
This question is more of a thought process one than asking for a code sample. What does a developer need in order to make such a major change in case it does not already exist?
Microsoft reveals OSK(on screen keyboard) for windows 10 iot core Creator update (build 15063) , it works good but i faced a problem! I want use it in other language layout , for example i need an on screen keyboard with Persian Layout that have Persian alphabet.
Does anyone have an idea to solve this ?
Working on version v.10.0.17661.1001.
To switch between languages, press and hold on the &123 key.
Note: This keyboard takes the place of the split keyboard layout.
Is it possible to change something in the touch keyboard in Windows RT?
For example, my app is a massive data entry. Many fields are alphanumeric IDs.
It is a mess to change all time from the numeric (123 key) to letter keyboard.
Is there a way to define which keys are included or excluded?
I used InputScope but it is very limited and no way to put numbers and letters in the same screen.
I'm Sorry, it is not possible to replace the touch keyboard on Modern UI in WinRT, without cracking.
Microsoft Windows RT Forum Hardware
Set the InputScope of your TextBox control to indicate what type of keyboard you would like for that text box. That's the best you can do. There is no facility for defining custom keyboard layouts in an application. (Keyboard layouts are considered a language feature, not an app feature.)
In Windows Phone, when the keyboard is up, there's usually a "suggestion line" above the keys.
For some languagea, this suggestion line is always there, such as eastern Asian languages.
For some other languages, like English, I can turn this off by going to "Settings" -> "Keyboard" -> "English" and uncheck "Suggest text".
And there are some languages that don't have suggestion line at all.
My questions is, how do I detect whether current keyboard has the suggestion line enabled or not?
No you cannot check that information through any API. In windows phone some API are not visible to developers. In your case also suggestion text information API is not accessible to developers for development.
How to get list of all available keyboards on Windows Phone Mango (in C# code)?
Or how to programmatically set custom keyboard for typing?
For example I want set the keyboard to Russian language for typing in my translator app to translate it into English
You can't change the keyboard language in code. That's up to the user. But with Mango, the user can have multiple keyboards, and switch with a single button press.
You should simply assume that the user will do this.
Here you will find a list of all available InputScopes -> http://www.kunal-chowdhury.com/2011/07/windows-phone-7-mango-tutorial-26-what.html