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
The font rendered properly in macOS for me, but I ran into this issue when checking out the new translation from a Windows 10 machine. It looks like we can package the font as a web font, so it may be possible to render the page for all users without having to manually download a font. We'd have to see if hugo can handle a remote font download and apply it for just this page. An alternative is to add a note to the top or bottom of the translation to download the font if the page doesn't render properly.
I don't think this should block merging, but it's something to keep in mind to fix up later.
The font rendered properly in macOS for me, but I ran into this issue when checking out the new translation from a Windows 10 machine. It looks like we can package the font as a web font, so it may be possible to render the page for all users without having to manually download a font. We'd have to see if hugo can handle a remote font download and apply it for just this page. An alternative is to add a note to the top or bottom of the translation to download the font if the page doesn't render properly.
I don't think this should block merging, but it's something to keep in mind to fix up later.
Originally posted by @klaude in #1051 (comment)
The text was updated successfully, but these errors were encountered: