by Michael S. Kaplan, published on 2012/08/02 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2012/08/02/10335988.aspx
Sean asked me the following contact request which I decided to make a blog:
MSKLC allows entry of unicode characters but complains if they aren't in the locale codepage. But there doesn't seem to be a way to set the codepage -- ugh. How do i tell - the keyboard/windows/whatever - to just work in Unicode and forget all this 1258 nonsense??? heh... sorry for my 4am desperate ramblings...
The message did indeed arrive at 4:26am. ;-)
The answer can be found under View|Options... and the Options dialog it launches:
That CheckBox over near the bottom right, the one that says Include Validation Warnings Related to Codepages one.
The help file topic explains how it works:
I'll tell you a secret.
Every single option on that dialog came from feedback from either the alpha pre-release or the beta pre-release, when someone gave me a keyboard layout with weird or strange behavior.
Like Sean's report, but earlier. :-)
At first I always warned, but then someone built a Hindi (Unicode only) keyboard.
So rather than a page of warnings covering nearly every key, I made it silently skip that validation for Unicode only locales.
Then someone else tried to build an Urdu keyboard -- code page 1256 but with many letters not on the codepage -- and she wanted a way to turn off those warnings entirely since those particular ones weren't useful in her case, ever though they could be important in other situations.
That's when I added that CheckBox.
Later, when someone building 15 different Arabic script keyboards who was sick of having to uncheck that CheckBox over and over.
Suddenly, the Remember Settings After Shutdown setting was born.
And so on....
Anyway, that should help Sean out.
Another time I'll tell you the exact reason why I was so sensitive about tons of spurious warnings....
go to newer or older post, or back to index or month or day