Addressing issues #168 related to not supporting multi byte characters

[talltyler]

JavaScript strings handle two byte characters as two items which breaks some multi lingual and emoji support.

Motivation and Context

This addresses #168

How Has This Been Tested?

npm test passes. And this has been tested in IE 11 and Chrome.

Types of changes

Mostly this just uses a for...of loop if the browser enables it. Because this is a new feature checks are made to make sure this method is available, and the build tools have been updated to support these changes.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I did npm run test and all tests passed green (including code styling checks).
• I have added tests to cover my changes.
• My change requires a change to the documentation.
• I have updated the README accordingly.
• I have read the CONTRIBUTING document.

[schuylr]

I tried your branch with a non-BMR character (this one: 🙂 ) on a font I made with a flat vector path (no colour like #193 mentions), and I still get a blank square. I'm using getPath and toPathData on the response.

[talltyler]

This branch doesn't solve any of the rendering issues these types of glyphs. It only allows multibyte characters to be passed through the system and handled as single units rather than two unrelated code points.

[schuylr]

I understand that, but I made a custom font with the same sort of glyphs that you would find in the ASCII/BMR range and it still didn't work. The result was still a blank square.

[talltyler]

Can you post this font and the character that you are passing in?

[schuylr]

Cursive.ttf.zip

The character I tried is above. "slightly smiling face" or U+1F642

[fpirsch]

Closed through #338