-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support U+1234 notation for Unicode symbols? #24
Comments
KLFC uses a normal JSON file, so you can use the syntax |
I find it to be somewhat «wrong» to let the format of serialization define the ways in which I may or may not define a symbol, for the following reasons:
I am sure this change is technically feasible. If someone were to make it, would you merge? |
I don't think it necessarily wrong to let the format decide it, but I understand that the intention may be lost as most parsers throw away that information. However, it is also not very elegant to basically make your own escape sequences. For example, ligatures can currently be written as |
I have now added explicit support for Unicode characters! |
I do observe that this feature works. If in the future we want to make sure ligatures can include strings that resemble the notation for Unicode code points, we can allow for the specification of a key to include not only strings, but objects like |
It is customary to denote Unicode characters by
U+[character code]
, but it seemsklfc
does not support this notation:Note that the character in this example is a kind of a space, so I would like not to insert it verbatim: it will hardly be clear for the reader what kind of space it is.
I also propose that there were a flag that allows writing
json
files withU+...
format. Most fonts only support a narrow range of characters, so in many cases the more unusual characters would not show in any meaningful way.The text was updated successfully, but these errors were encountered: