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
Currently, when we use the createWithTTF API call for Arabic texts, we get texts in the opposite direction than what we expect(Left to Right). It is not just that, but we do not get the exact opposite of the passed string. If there are characters that combine to form new characters, we do not get that operation working.
This could be happening due the lack of a shaping engine like Harfbuzz. We can only get Arabic texts working as expected when we use the createWithSystemFont API. However with that call, we cannot use a custom font.
The text was updated successfully, but these errors were encountered:
Currently, when we use the createWithTTF API call for Arabic texts, we get texts in the opposite direction than what we expect(Left to Right). It is not just that, but we do not get the exact opposite of the passed string. If there are characters that combine to form new characters, we do not get that operation working.
This could be happening due the lack of a shaping engine like Harfbuzz. We can only get Arabic texts working as expected when we use the createWithSystemFont API. However with that call, we cannot use a custom font.
The text was updated successfully, but these errors were encountered: