wezm/wezm.net
1
0
Fork 1
mirror of https://github.com/wezm/wezm.net.git synced 2024-11-17 20:38:01 +00:00
Code Issues Projects Releases Packages Wiki Activity

Kobo post updates

Browse source
This commit is contained in:
Wesley Moore 2024-11-14 18:16:33 +10:00
parent 43667e68b9
commit 06b899d74b
No known key found for this signature in database
1 changed files with 13 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
v2/content/posts/2022/monospace-kobo-ereader/index.md
View file

@ -3,7 +3,7 @@ title = "Fixing Monospace Text in Kobo eReaders"
date = 2022-04-10T09:14:50+10:00
[extra]
updated = 2022-08-22T14:10:50+10:00
updated = 2024-11-14T18:10:31+10:00
+++
After verifying with friends that eBook readers do a decent job of rendering
@ -14,6 +14,18 @@ text with CSS rules like `font-family: monospace` in a monospace font.
<!-- more -->
**Update Nov 2024:** Oliver Fink wrote in to tell me that the issue is that
the font now has to have the font family name "Courier", not just have a
file name of Courier. [Check out their write-up][olifink] for all the details.
Additionally Roman Frołow wrote in with a tip for a tool that can turn off
behaviour that overrides the font family in KePub books, which could also
result in monospace fonts not showing up in books. [Visit this Reddit
thread][rofrol] for the details.
[olifink]: https://memos.mountmerlin.com/m/Gy8venDj6xej3vabw2idwx
[rofrol]: https://www.reddit.com/r/kobo/comments/12kgo49/comment/jg4p6gj/
**Update Aug 2022:** I was told and have confirmed myself that the workaround
described in this post no longer works with the latest firmware. I tested
version 4.33.19759. If anyone knows how to restore the behaviour please get in