Closed yayachiken closed 4 years ago
I am not familiar when it comes to multilingual font support... so:
Do you think that Firefox itself has an issue, and this is why Chrome shows it fine?
Or, do you think that this theme has an issue, and Chrome is doing some silent error handling?
I am not familiar when it comes to multilingual font support... so:
Do you think that Firefox itself has an issue, and this is why Chrome shows it fine?
Or, do you think that this theme has an issue, and Chrome is doing some silent error handling?
@yayachiken ?
Closing this issue for reasons:
Sorry that I do not immediately respond within my own leisure time.
The root cause is as I said already: The fonts packaged with the theme are broken. Redownloading the Miriam Libre Bold font from Google helps, the font size gets increased by about 5 kB per file (woff/woff2) so that's a bit of a tradeoff for better i18n (it seems that other European languages are affected by the broken fonts as well.)
I would have filed a PR eventually, but if you are that impatient, you will have to do that by yourself now. The information I gave should be well sufficient to fix this on your own.
Again sorry for wasting your time.
You opened the issue 16 days ago. Keep in mind this is my leisure time as well.
If I came off harsh, that is not my intent. If someone were to submit a PR for this, I would gladly review it.
Fixed by @fkohrt in https://github.com/zwbetz-gh/cupper-hugo-theme/pull/43
Please verify @yayachiken
I have not tried out this specific commit, but it seems @fkhort implemented the fix I described (redownloading fonts) , so this should be alright.
Describe the bug German Umlaut characters and Eszett (ÄÖÜäöüß) do not render in headline font in Firefox.
To Reproduce Steps to reproduce the behavior:
Expected behavior Chrome and Firefox render the fonts the same, especially the special characters should fit in.
Screenshots
Example 1 from a real page (note the headlines):
Example 2 from fontdrop.info:
Desktop (please complete the following information):
Additional context I was also able to reproduce the behaviour by uploading the woff font to https://fontdrop.info/ and putting in the above mentioned text in the "Type yourself" field, maybe only the woff font is broken and woff2 works?