You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Inkle Studio’s narrative scripting language editor, Inky, on a Mac, Korean characters written in Unicode often appear fragmented, making it impossible to display them correctly.
This issue seems to stem from Ink utilizing the NFD (Normalization Form Canonical Decomposition) method for Unicode normalization, rather than NFC (Normalization Form Canonical Composition). To display Korean characters correctly, the NFC normalization form must be used.
The text was updated successfully, but these errors were encountered:
cheng80
changed the title
The issue of Korean character fragmentation in Ink
The issue of Korean character fragmentation in Inky
Jan 23, 2025
Autocompletion for unicode is actually not supported since the version of ace editor used in inky does not yet support unicode regex. Because of that I'd recommend using ascii only for symbols like knots and variables.
The tree-siitter-ink project should support unicode fully #934, but I need to implement a language-server based on tree-sitter-ink before it is a full IDE:
When using Inkle Studio’s narrative scripting language editor, Inky, on a Mac, Korean characters written in Unicode often appear fragmented, making it impossible to display them correctly.
This issue seems to stem from Ink utilizing the NFD (Normalization Form Canonical Decomposition) method for Unicode normalization, rather than NFC (Normalization Form Canonical Composition). To display Korean characters correctly, the NFC normalization form must be used.
The text was updated successfully, but these errors were encountered: