[GH-ISSUE #1302] Visual Bug: Default font does not properly support Cyrillic characters #6345

Closed
opened 2026-04-20 16:55:55 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @imKeim on GitHub (Aug 17, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1302

Description

The default font, Quicksand, does not include Cyrillic characters. This causes the browser to fall back to a system font for any Cyrillic text.

The result is a jarring mix of different font styles (Quicksand for Latin, a system font for Cyrillic) on the same screen, which disrupts the otherwise polished user interface and affects readability. I've attached a screenshot that clearly demonstrates this issue on the main page and within a task view.

Suggested Solution

To ensure a consistent visual experience for all users, here are a few possible approaches to fix this rendering bug:

  1. Font Pairing: Use a complementary Cyrillic font alongside Quicksand. A font like 'Nunito' or 'Montserrat' could be loaded specifically for Cyrillic character ranges. This would preserve the original design for Latin-based languages while providing a consistent look for others.

  2. Custom Font Support: In the long term, allowing users to specify their own custom fonts in the settings would be a fantastic feature. This would solve the issue for all languages and provide a great deal of flexibility.

Thank you for your hard work on this fantastic project!

Vikunja Version

Latest Unstable

Browser and version

Firefox on PC and Chrome on Android

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image Image
Originally created by @imKeim on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1302 ### Description The default font, Quicksand, does not include Cyrillic characters. This causes the browser to fall back to a system font for any Cyrillic text. The result is a jarring mix of different font styles (Quicksand for Latin, a system font for Cyrillic) on the same screen, which disrupts the otherwise polished user interface and affects readability. I've attached a screenshot that clearly demonstrates this issue on the main page and within a task view. **Suggested Solution** To ensure a consistent visual experience for all users, here are a few possible approaches to fix this rendering bug: 1. **Font Pairing:** Use a complementary Cyrillic font alongside Quicksand. A font like 'Nunito' or 'Montserrat' could be loaded specifically for Cyrillic character ranges. This would preserve the original design for Latin-based languages while providing a consistent look for others. 2. **Custom Font Support:** In the long term, allowing users to specify their own custom fonts in the settings would be a fantastic feature. This would solve the issue for all languages and provide a great deal of flexibility. Thank you for your hard work on this fantastic project! ### Vikunja Version Latest Unstable ### Browser and version Firefox on PC and Chrome on Android ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots <img width="1080" height="2400" alt="Image" src="https://github.com/user-attachments/assets/cf896a56-2784-4f70-912b-4fb5e8cb3f7f" /> <img width="1080" height="2400" alt="Image" src="https://github.com/user-attachments/assets/6794705b-73d6-40a0-8271-fea3118a449f" />
Author
Owner

@kolaente commented on GitHub (Aug 17, 2025):

Related to https://github.com/go-vikunja/vikunja/issues/143

<!-- gh-comment-id:3194641197 --> @kolaente commented on GitHub (Aug 17, 2025): Related to https://github.com/go-vikunja/vikunja/issues/143
Author
Owner

@kolaente commented on GitHub (Aug 17, 2025):

Fixed in eb676aebef, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

Note that Quicksand, the font we're using for headings, does not support Cyrillic. However, I've updated the text font we're using to include Cyrillic glyphs.

The size increase is still small.

Before:

40K Aug 17 22:59 'OpenSans-Italic[wght]_efd8026f.woff2'
36K Aug 17 22:59 'OpenSans[wght]_e4849d7d.woff2'
33K Aug 17 22:59 'Quicksand[wght]_6d82d68f.woff2'

After (with all languages):

85K Aug 17 23:05 'OpenSans-Italic[wght]_f8c82d6f.woff2'
79K Aug 17 23:05 'OpenSans[wght]_0f3a8072.woff2'
37K Aug 17 23:05 'Quicksand[wght]_a912b486.woff2'
<!-- gh-comment-id:3194655536 --> @kolaente commented on GitHub (Aug 17, 2025): Fixed in eb676aebef4864e12827c4e9c51f3d561cd29cdf, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)). Note that Quicksand, the font we're using for headings, does not support Cyrillic. However, I've updated the text font we're using to include Cyrillic glyphs. The size increase is still small. Before: ``` 40K Aug 17 22:59 'OpenSans-Italic[wght]_efd8026f.woff2' 36K Aug 17 22:59 'OpenSans[wght]_e4849d7d.woff2' 33K Aug 17 22:59 'Quicksand[wght]_6d82d68f.woff2' ``` After (with all languages): ``` 85K Aug 17 23:05 'OpenSans-Italic[wght]_f8c82d6f.woff2' 79K Aug 17 23:05 'OpenSans[wght]_0f3a8072.woff2' 37K Aug 17 23:05 'Quicksand[wght]_a912b486.woff2' ```
Author
Owner

@kolaente commented on GitHub (Aug 17, 2025):

Sorry, read the issue again.

Supporting another font at the same time is not really in scope right now. There are plans to change the font in general, but that will take a while. Still, I'd rather focus on that instead of adding a workaround.

cc @dpschen

<!-- gh-comment-id:3194656696 --> @kolaente commented on GitHub (Aug 17, 2025): Sorry, read the issue again. Supporting another font at the same time is not really in scope right now. There are plans to change the font in general, but that will take a while. Still, I'd rather focus on that instead of adding a workaround. cc @dpschen
Author
Owner

@imKeim commented on GitHub (Aug 18, 2025):

Thank you for the quick response and for the partial fix! I understand your reasoning about not wanting to add a workaround. It's great to hear that a general font change is planned for the future. I'll check the unstable build for the text font improvements.

<!-- gh-comment-id:3194990813 --> @imKeim commented on GitHub (Aug 18, 2025): Thank you for the quick response and for the partial fix! I understand your reasoning about not wanting to add a workaround. It's great to hear that a general font change is planned for the future. I'll check the unstable build for the text font improvements.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6345