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
Discovered an interesting "bug", although maybe I'm stretching the tool beyond its intended use.
In the FontInfo makeJSON function, there are several places where a character is converted to (byte). This assumes ASCII characters. Simply swapping that to (int) seems to make it UTF8 friendly. (Character values like int of 61440, etc). It otherwise handles it just fine.
Not sure if you still maintain this, but in case, there you go.
The text was updated successfully, but these errors were encountered:
Discovered an interesting "bug", although maybe I'm stretching the tool beyond its intended use.
In the FontInfo makeJSON function, there are several places where a character is converted to (byte). This assumes ASCII characters. Simply swapping that to (int) seems to make it UTF8 friendly. (Character values like int of 61440, etc). It otherwise handles it just fine.
Not sure if you still maintain this, but in case, there you go.
The text was updated successfully, but these errors were encountered: