feat: add Vazirmatn fallback font for Arabic/Persian

[ammahmoudi]

Bundles Vazirmatn (WOFF2) in public/font/vazirmatn/ to avoid runtime external font requests.
Adds @font-face with Arabic unicode ranges and includes OFL.txt.
Updates the global font stack to use Vazirmatn as a fallback after Inter, so Arabic/Persian text renders more cleanly without changing the UI font for everyone.

[kfiven]

Hi, what is the issue you are having?

[ammahmoudi]

Hi! The current default font doesn't render Persian and Arabic characters optimally, which affects legibility. Adding Vazirmatn as a fallback significantly improves readability and typographic balance for native readers, providing a much better user experience for these languages. Vazirmatn is common in apps with nice support for rtl users.

[u9000-Nine]

See also Add ability to change the font · Issue #2619 · cinnyapp/cinny (Farside)

[kfiven]

Thoughts on https://fonts.google.com/noto ?

I myself is multilingual and looking at noto, they support wide variety of languages, which would be better approach rather than adding font for each language.

[Behzad9]

Thoughts on https://fonts.google.com/noto ?

I myself is multilingual and looking at noto, they support wide variety of languages, which would be better approach rather than adding font for each language.

While it is true that noto fonts provide broad multilingual coverage, Vazirmatn is specifically optimized for Persian and other RTL languages. It is widely used in RTL contexts and is currently the default Persian font in X, reflecting its strong adoption.

[dembim]

In general, I don't think adding a new fallback font for every script that renders incorrectly (which is most of them at the moment, as far as I can tell) is a scalable solution. A more broadly suitable approach is to allow in-client configuration of fonts, including system-provided fonts, so that rendering concerns for non-latin scripts can be handled on an individual basis. See the above-linked issue on adding such support.

[ammahmoudi]

In general, I don't think adding a new fallback font for every script that renders incorrectly (which is most of them at the moment, as far as I can tell) is a scalable solution. A more broadly suitable approach is to allow in-client configuration of fonts, including system-provided fonts, so that rendering concerns for non-latin scripts can be handled on an individual basis. See the above-linked issue on adding such support.

I agree that user-configurable fonts (#2619) is valuable, but it doesn’t fully solve this problem in practice for Arabic/Persian:

• Many users (especially on mobile) can’t realistically install additional system fonts, so “pick a system font” often won’t include something like Vazirmatn.
• A lot of real usage is mixed English + Persian/Arabic. A good fallback stack is the common approach in chat apps (Telegram-style), because it preserves the Latin UI typography while improving Arabic-script readability.
• This PR is intentionally narrow: it adds a single Arabic-script fallback via unicode-range, so it doesn’t change Latin UI rendering and doesn’t attempt to add “a font per script”.

If maintainers still prefer “config-only”, I understand. But I think a targeted Arabic-script fallback is a practical baseline improvement for a large user group, while font configuration can remain an additional power-user feature.

[Behzad9]

I believe this feature would significantly improve readability and typographic balance for RTL users.

[Alen21137]

I have also requested this feature in several other places, and it could be very beneficial for all Persian/Arabic users.