Hoping to test out your latest Keyman program, I installed TIKE 6.1.166.1. I used a .kmn file that was successfully compiled, installed and used for a Tahoma unicode .ttf.
However, when I tried to view the characters of a Bitstream Vera Se unicode font that I have modified (modified using FontLab 4.6) some of the unicode characters -- when viewed in TIKE Character Map -- do not have the correct unicode assigned to them. Instead, "U+0000" displays beneath the glyphs in the TIKE Character Map.
I also viewed the SIL Gentium unicode font in TIKE Character Map but some of those glyphs have been assigned "U+0000" by TIKE, apparently. However, when I use the Windows Character Map to view these same two unicode fonts, the correct code is assigned to them there and they are accessible to other text applications using the corresponding "alt + XXXX". I can get the characters entered into TIKE, to format the .kmn, this way and I wonder if this method is a functional work-around for this particular problem? Have other people had this same problem? I'd prefer to find out now rather than discover this later -- only after after I have laboriously formatted the TIKE Keyman .kmn with unicode using the Windows Character Map method.
Is this problem unique to my situation, or is it a typical problem one encounters with TIKE and unicode?
Thank you.
Topic XP Pro, TIKE and Keyman
We have two new locations for Keyman technical support:
- SIL Keyman Community - for general Keyman technical support
- Stack Overflow - for support on creating keyboard layouts with Keyman Developer
The Tavultesoft Forums are now read only.
| # XP Pro, TIKE and Keyman 2005-11-18 14:08:15.000 | |
|---|---|
| twaits | |
| # 2005-11-18 19:57:25.000 | |
| mcdurdin Tavultesoft Staff | This is an issue that has been resolved in the latest release of Keyman Developer, 6.2.175.0.
Regards, Marc Durdin Tavultesoft Pty Ltd |