So, the second problem I’m having is contextual substitution (and kerning, for that matter) in RTL orientation. My font works as follows: you enter the code for a particular symbol, let’s say N14, and through a custom font feature that essentially works like a ligature, the proper symbol is shown:
sub [n N] one four by u131FC;
I decided to go this route so that anyone typing either online or in DTP software, can work with the codes they’re used to. The font takes care of the rest.
So anyway, the webfont works perfectly in Safari:
But, when using my webfont in chrome, the contextual alternates algorithm is still reading LTR, so it’s taking N14G1 (which in RTL looks like 1G41N) and substituting G41 instead.
In that last screenshot, I did a test showing that if I enter 41N I get the symbol N14.
Am I missing something? Do I need to set up the language settings differently in the font? Does anyone know why this is working in Safari, but not in Chrome?
Any help would be greatly appreciated!!!