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
Desktop (please complete the following information):
OS: [e.g. iOS] Windows
Browser [e.g. chrome, safari] Firefox
Version of the Theme v1.13.0
Version of Hugo (run a hugo version if unsure) hugo v0.121.2-6d5b44305eaa9d0a157946492a6f319da38de154+extended windows/amd64 BuildDate=2024-01-05T12:21:15Z VendorInfo=gohugoio
Additional context
The text was updated successfully, but these errors were encountered:
Hmm, I can't replicate it on my MBP, but it was originally encountered and filed on my Windows machine. I'll try replicating when I get back today, but it's possible the issue was with the font installation on that specific Windows computer and/or was fixed in the interim. If that's the case I will close the issue.
OK, I can still replicate it on Chrome/Firefox, on Windows at least. (Linux not checked yet.) My blog is running v1.14.0, and Chrome is on 126.0.6478.127, Firefox on 127.0 (and 128.0).
See the differences below.
English version:
Korean version:
It's like this thin/light font for the codeblocks.
Firefox reports that the English version uses the Arial font, while the Korean one uses GulimChe. I think for Korean at least, something like the Nanum font from Naver (https://hangeul.naver.com/font) may be more suitable. (It is also free to use for commercial purposes as long as the font pack itself is not resold if I understand the terms correctly.)
Describe the bug
Currently the code font for Korean-translated blog posts is weird. See this link for an example:
https://ericswpark.com/ko/blog/2021/2021-11-13-terminal-incognito-mode/
Screenshots
Desktop (please complete the following information):
hugo version
if unsure) hugo v0.121.2-6d5b44305eaa9d0a157946492a6f319da38de154+extended windows/amd64 BuildDate=2024-01-05T12:21:15Z VendorInfo=gohugoioAdditional context
The text was updated successfully, but these errors were encountered: