I happened upon two versions of the same Korean unicode string: 인스타 and 인스타. As you can see from the unicode inspector the first uses multiple codes per character from the Hangul Jamo block whereas the second uses a single code per character from Hangul Syllables.
The weirdness is when they are rendered in page alongside other characters, as you can see when I tested the following in Google Fonts:
인스타 abc 인스타
인스타 123 인스타
...renders as...
I'm assuming it is a bug in the browser render engine rather than the font, but this seemed like the right place to start the escalation process.
I happened upon two versions of the same Korean unicode string: 인스타 and 인스타. As you can see from the unicode inspector the first uses multiple codes per character from the Hangul Jamo block whereas the second uses a single code per character from Hangul Syllables.
The weirdness is when they are rendered in page alongside other characters, as you can see when I tested the following in Google Fonts:
인스타 abc 인스타 인스타 123 인스타
...renders as...
I'm assuming it is a bug in the browser render engine rather than the font, but this seemed like the right place to start the escalation process.