Thread: CSS to Approximate a Telegram?
View Single Post
Old 09-01-2022, 11:04 AM   #17
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,238
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Quoth View Post
Embedding fonts for Kobo isn't a problem. But if monospace is done right then the basic mobi version made by Amazon will work.

So no "small caps" use CAPS SOURCE. It's a Telegram, not a paragraph intro.
Do the CSS with an embedded monospace font of choice and declares to suit things that don't use embedded.

I have formatted ebooks simply by converting docx and had monospace (for a Terminal session) work on everything (kepub, epub, same epub to Amazon and download sale of mobi, azw3 and KFX).
The font engine in Kobo has change since firmware 4.32. So you now need to embed a monospace font for KePub and in fonts you need one called Courier (internal font name).
JSWolf is offline   Reply With Quote