mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-22 06:11:08 -05:00
Font missing diacritics characters #135
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sq3tle on GitHub (Apr 24, 2023).
Originally assigned to: @dpschen on GitHub.
Description
Font used in sidebar and task editing panel is missing diacritics characters used in Polish language. In case of some languages, it may be worth to fallback to some regular font.
Vikunja Frontend Version
0.20.5
Vikunja API Version
0.20.4
Browser and version
chrome 112.0.5615.138
Can you reproduce the bug on the Vikunja demo site?
Yes
Screenshots
@dpschen commented on GitHub (Apr 24, 2023):
Seems like our font subsetting script needs to be extended to support
latin-ext. One way could be to extend theSUBSETTER_ARGSargument of theinstance_and_subsetfunction to support an array of subsetting arguments. For each element of the array we would create a new output file.Looking at Googles subsets of OpenSans I'm pretty sure, that there are currently similar problems with our Vietnamese translations.
We need to adjust the preloading of the font as well based on the selected language
@orhid commented on GitHub (Apr 11, 2025):
has there been any movement on this bug?
@dpschen commented on GitHub (Apr 15, 2025):
No, but I try to fix this soon (will try this week). Since our internationalisation has progressed a lot this became more urgent.
@sceptri commented on GitHub (Jul 16, 2025):
Hey, just wanted to ask... any update on this bug?
@kolaente commented on GitHub (Jul 17, 2025):
I've adjusted this in
aea2f708d3- please check with the next unstable build (should be ready for deployment in ~30min, also on try).@dpschen This was the fastest way to fix the problem here, feel free to optimize this further.
@dpschen commented on GitHub (Jul 17, 2025):
All good. Sry that i didn’t get to this yet.
@kolaente I‘m a bit confused that you didn’t need to change the unicode range.
@kolaente commented on GitHub (Jul 17, 2025):
@dpschen I did:
3b8258d57e