-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"dead key is not defined" when converting from .klc #35
Comments
Here's the full text of the input file, for easier viewing. The input contains the dead key definition.
|
And here's the output json file. The output does not contain the dead key definition.
|
That line if where the magic's supposed to happen, right? AltGr+Shift+Apostrophe should produce the Sheva dead key. I've experienced that you cannot always use non-ASCII marks for dead key names. Maybe that's your problem. Try calling your dead key period instead of sheva. You can still have it output exactly the same symbols as it does now! Oh, and while I have your attention: Could you please take the time to swing by my EPKL repo and tell me what you think of the phonetic Colemak layout there? I'm a bit stoked about inventing those dead keys on O and Y for writing niqqud and so much more. https://github.com/DreymaR/BigBagKbdTrixPKL/tree/master/Layouts/Colemak/Cmk-eD-Heb |
How do I change the "name" of a dead key without changing the actual definition? (Note that in many word processors, pressing the dead key and then pressing any character other than those the dead key maps will send the actual character of the dead key, followed by the character you typed.) Your keyboard layout is definitely interesting, although I'm not that familiar with Colemak in general. I would say that I definitely prefer using AltGr and AltGr+Shift for nikud as opposed to dead keys, but that's just my personal preference. I find that the segregation of anything nikud-related to the AltGr key makes my life easier because 99% of the time I'm not using nikud. |
Change the Niqqudot is a conundrum, for sure. Most people nearly never use it, but I think that if you are to use them then AltGr mappings would make that very uncomfortable. For a "1%" use case that's okay but for a scholar it wouldn't be cool. The dead keys, furthermore, can release a lot more than just niqqud including special Hebrew characters and Yiddish. I'm taking that further now by including a Compose method so you could for instance compose a yod-yod bigram to a yod-yod digraph. EPKL is a fun project! |
The dead key works properly on Windows, so this isn't a problem with MSKLC, it's a problem with this conversion tool. I think I'll leave it as-is for now, I'm not really using any of the other platform formats right now anyway. Maybe I'll add something to my conversion script to make a copy with the sheva dead key replaced with a period, and convert from that. |
Yeah, I'm just guessing at why Aldo's tool might have a problem with that DK. I'd still recommend that you follow the convention of including a space release for your dead key. All standard DKs have that, ttbomk. An example from my own layout, where I also made a NBSP release for the combining accent:
|
I'll add it in |
There was an issue with the KLC parsing: it behaved like the ligature part extended to the end of the file (with most having no values of course). I have pushed a fix, but as a workaround you can simply put the |
When converting a certain .klc file (attached), I get the error
klfc: warning: dead key ‘ְ’ is not defined.
, and the converted output files (also attached) do not contain the dead key definition. The dead key is definitely defined, on lines 95-102 of the input. I've attached my input file, as well as all of the output files produced by the conversion (which do not include the dead key).he_phon.klc.txt (renamed to .txt to attach)
output.zip (zipped)
The text was updated successfully, but these errors were encountered: