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
It would be awesome to have true i8n support, but I'm not sure how the encodings work or how one would go about converting a unicode string into them.
Perhaps they could have a documentation link, or, maybe even better yet, the fonts could have a character map?
Seems like the layout doesn't quite follow the ordering Unicode uses, but most blocks seem to be less than 256 chars, so it should be possible to translate codepoints to whatever special thing this uses just by offsetting and doing an array lookup.
It wouldn't give you LTR support, but it would make symbols and RTL languages easier.
The text was updated successfully, but these errors were encountered:
It would be awesome to have true i8n support, but I'm not sure how the encodings work or how one would go about converting a unicode string into them.
Perhaps they could have a documentation link, or, maybe even better yet, the fonts could have a character map?
Seems like the layout doesn't quite follow the ordering Unicode uses, but most blocks seem to be less than 256 chars, so it should be possible to translate codepoints to whatever special thing this uses just by offsetting and doing an array lookup.
It wouldn't give you LTR support, but it would make symbols and RTL languages easier.
The text was updated successfully, but these errors were encountered: