by Michael S. Kaplan, published on 2008/08/08 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/08/08/8842353.aspx
Christopher's question to me was not my favorite kind of inquiry:
Hi Michael. A simple question, I hope: It appears to me that the MSKLC (v1.4) doesn't see any installed Type 1/CFF-flavor fonts. Is this true? Makes it difficult to test keyboard layouts created for such fonts... :(
Thanks,
Christopher
The reason that this isn't my favorite kind of question?
Well, mainly since the answer is so unfortunate....
Microsoft Keyboard Layout Creator is a managed WinForms application, heavily dependent on GDI+.
Because of that, the lack of support for Type 1 fonts in GDI+ is a pretty blocking issue for the display of text within the MSKLC user interface.
The one good thing here about all of this is that you can still build the keyboard, using Unicode code points and such, and then you can build and install the keyboard to test it out. Not ideal, but at least it is possible....
This "using the force" method to develop a keyboard layout was how I was able to build a test layout for Deseret when I was first testing out MSKLC's support of supplementary characters, when I did not have a Deseret font to test with.
This blog brought to you by 𐐑 (U+10411, aka DESERET CAPITAL LETTER PEE)
# Aidan Kehoe on 8 Aug 2008 7:54 AM:
The file format is agreeably simple, too.
# Adam T on 9 Aug 2008 8:35 AM:
You can use TransType Pro (http://www.fontlab.com ) to convert an OpenType PS (.otf) font to an OpenType TT (.ttf) font, which will allow you to easily test your keyboard.