experchange > win32.programmer.* > win32.programmer.international

Patrick Philippot (06-14-04, 02:04 PM)
Hi,

I have created a layout with MSKLC but after a succeeded validation the
compilation process fails:

cl.exe returned 1
rc.exe returned 1
link.exe returned 1

Any idea?

Thanks in advance.
Michael \(michka\) Kaplan [MS] (06-14-04, 03:01 PM)
Hmmm.... what version of MSKLC?

If its the latest version (just put up within a month or so), then can you
send the .KLC file of the layout that repros the problem to
michka?
Patrick Philippot (06-14-04, 03:21 PM)
Michael (michka) Kaplan [MS] wrote:
> Hmmm.... what version of MSKLC?
> If its the latest version (just put up within a month or so), then
> can you send the .KLC file of the layout that repros the problem to
> michka?


I'm using the latest. I just sent the keyboard to your maibox file but
I don't think it's tied to the keyboard file itself. I tried with
multiple layouts.

Thanks.
Michael \(michka\) Kaplan [MS] (06-14-04, 03:51 PM)
Yep, got it. But I cannot repro the problem....

Out of curiousity, what is your user locale? I would not expect this to make
a difference but we do use the C runtime and one never knows what it will
do, right?
Michael \(michka\) Kaplan [MS] (06-14-04, 04:25 PM)
Ok, we found out the problem (well, Patrick put in most of the skull sweat!
<grin>).

The problem is on a system with 8.3 file names (aka short file names)
disabled -- since the default install dir is in "Program Files" and has
other spaces in the app dir, the tool converts to short file names for the
compile, which obviously fails when short file names are disabled. The
workaround would be to install MSKLC to a directory that does not have
spaces in the path.
abdelouahidmdaghri (07-07-14, 09:24 PM)
hello i have the same problem can u show me how to fix. thanks
jkooten.zigwebsoftware (02-09-15, 04:37 PM)
I tried to find out whether my system (Win 8) had 8.3 names disabled or notbut could not find it. Turns out it was a lot faster to simply copy the contents of the MSKLC folder into a folder without spaces or long names (I used C:\keys\msklc) and run msklc.exe from there. Now it works. (I am going to uninstall the installed version of MSKLC so double clicking on a KLC filedoesn't open the installed version.)

For an official MS product I think this is rather shameful.

On Monday, June 14, 2004 at 4:25:40 PM UTC+2, Michael (michka) Kaplan [MS] wrote:
[..]
etremel (08-19-15, 12:13 AM)
Hello,

Display of fonts with glyphs of Unicode ranges from hex-10000 upwards.
(Example glyphs of Unicode ranges from hex-10b00 to hex-10b3f (Avestan)
and from hex-10b78 to hex-10b7f (Inscriptional Pahlavi))

They are not displayed correctly in Microsoft features like Word or managed in Keyboard Layout Creator?
cf:


In Unicode Code Unicode 6.0.0_6.1_6.2_6.3_7.0.0-8.0 there are many glyphs from ranges hex-10000 (Linear B Syllabary)
up to hex-e01ef (Variation Selectors Supplement).

As far as I can see the above mentioned problems are not yet solved neither in Windows 8.1
nor in the newest version of Windows 10.

What's the matter? Why these difficulties with these Unicode Code ranges?

Does Office 365 or Office 2016 support these above described Unicode ranges ?
E.g. Keyboards for Avestan, Inscriptional Pahlavi, Linear B Syllabary and so on?

Until today - since some years ago - I'm still waiting getting these problems being solved in Microsoft's features, but how and when?

Regards,
Ernst Tremel
gabelogan1324 (09-29-15, 04:49 PM)
On Monday, February 9, 2015 at 2:37:46 PM UTC, jkooten.zig...@gmail.com wrote:
> I tried to find out whether my system (Win 8) had 8.3 names disabled or not but could not find it. Turns out it was a lot faster to simply copy the contents of the MSKLC folder into a folder without spaces or long names (I used C:\keys\msklc) and run msklc.exe from there. Now it works. (I am goingto uninstall the installed version of MSKLC so double clicking on a KLC file doesn't open the installed version.)
> For an official MS product I think this is rather shameful.
> On Monday, June 14, 2004 at 4:25:40 PM UTC+2, Michael (michka) Kaplan [MS] wrote:


I agree as well; quite shameful indeed
whaefelinger (07-21-17, 03:58 PM)
2017 - problem still exists MKLC 1.4 and Windows 7 (Enterprise).

On Monday, 14 June 2004 14:04:59 UTC+2, Patrick Philippot wrote:
[..]
whaefelinger (07-21-17, 04:08 PM)
Ok, the rather obvious workaround is to install MSKLC into a custom folder having no blanks, i.e. something like c:\msklc.

Doing so, everything works as expected.
j.potocnjak.l (01-11-18, 02:18 AM)
After trying and trying I found this chain-mail and finally I'm able to install the keyboard, Thank you very much!
gisnook (01-25-18, 12:35 PM)
Indeed, it works now.

My MSKLC was not even installed in the Programmes folder but in « My Documents », in the same folder together with the keyboards..

Moved it to « C:\ » and then everything perfect.

Thank you everyone !
henriquebrisola (12-21-18, 10:47 PM)
That helped me today, was trying to have this working for a long time.
Thanks!