Inaccurate syntax highlighting after unicode characters

[Mees0x4E]

If you type a unicode character (some characters work, some don't), and then anything that gets syntax highlighting in the APDE editor (for example: ₱ draw() 🏳️ width ✓ null ), the syntax highlighting is offset from the actual text. However, if the unicode character is in a string, the purple syntax highlighting in that string looks normal, but any syntax highlighting after the end-quote still looks odd (for example: "→ test" "test" ).

[Calsign]

This is a known issue, due to the way that the syntax highlighter counts characters (it expects that each character is one "m" wide, but Unicode characters actually occupy multiple character slots). I am planning a major rewrite of the syntax highlighter and intend to fix this issue then.