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
Describe the bug
Rendering various characters in Unicode is currently inconsistent and can be improved by using an updated custom font.
To Reproduce
Steps to reproduce the behavior:
Open any Shabad in a WebKit browser, enable Unicode
Open the same Shabad in a Chromium and Gecko browser
Rendering of characters such as Ik Oangkaar may be inconsistent.
Expected behavior
Gurmukhi should render consistently in all browsers, apart from issues with bindi/tippi placed before bihari. An updated Gurmukhi Unicode font should be used. Akaash is a good option as it is regularly maintained and very similar to GurbaniAkhar and AnmolUni (the legacy Unicode font used in Khalis applications).
Describe the bug
Rendering various characters in Unicode is currently inconsistent and can be improved by using an updated custom font.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Gurmukhi should render consistently in all browsers, apart from issues with bindi/tippi placed before bihari. An updated Gurmukhi Unicode font should be used. Akaash is a good option as it is regularly maintained and very similar to GurbaniAkhar and AnmolUni (the legacy Unicode font used in Khalis applications).
Screenshots
Refer to this issue from anvaad-js
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Akaash font download
The text was updated successfully, but these errors were encountered: