Typeface Question - Page 2

petrjahoda · 10-20-2026, 09:48 AM

So this is how it is done as a 'beta' version.
It can work as today, until 'Fonts by Style' is enabled.
Then you can set it like you suggested (this goes for culytera).
And it also detects other texts presented in the book, in the example text set up as times new roman (maybe some info text or what).

What do you say, culytera, ok?
So a normal user, like me, will not use this option.
And advanced user, like you, have the ability to play with it more.

mikepmiller · 10-20-2026, 10:57 AM

Wow! I know you were asking for culytera's opinion, but for what it's worth, that looks fantastic to me. Thanks!!

culytera · 10-20-2026, 11:00 AM

Yeah, that looks great!

petrjahoda · 10-20-2026, 11:03 AM

OK, I will build the functionality tomorrow, this si just a design made inside the app without working code.
Thank you for ideas, will be in 5.6

JSWolf · 10-20-2026, 11:41 AM

Quote:

Originally Posted by petrjahoda

OK, I will build the functionality tomorrow, this si just a design made inside the app without working code.
Thank you for ideas, will be in 5.6

Before you being coding this, how are you doing the headings? Are you modifying the h styles? You also left out the spacing around the heading. The problem with the heading is not the size but the excess space around chapter headers. You have no control over the spacing.

If you do this by modifying h styles, then what happens when the same h is used someplace else?

petrjahoda · 10-20-2026, 11:52 AM

Yes, I am aiming all <h> tags, so if this tag is used somewhere else, it will be treated the same way. But good point, I think I will be able to aim only for h tags at the start of chapter.
And I will also look at those spaces. They do not bother me at all, but looks like they can bother others. Now I have no idea, what and how can be done with it, but I did not look into this yet.

Thank you for it.

JSWolf · 10-20-2026, 01:45 PM

Quote:

Originally Posted by petrjahoda

Yes, I am aiming all <h> tags, so if this tag is used somewhere else, it will be treated the same way. But good point, I think I will be able to aim only for h tags at the start of chapter.
And I will also look at those spaces. They do not bother me at all, but looks like they can bother others. Now I have no idea, what and how can be done with it, but I did not look into this yet.

Thank you for it.

What are you going to do if the chapter starts with a <p>? A lot of eBooks use something like <p class="chapternumber">

Another problem comes if the chapter title has a subtitle. Sometimes the subtitle (or there text) has an h or a p.

IMHO, there seems to be too many barriers to allow editing the chapter titles cleanly.

petrjahoda · 10-20-2026, 01:55 PM

So in the meantime I made some tests.
1. I will target headings at starts of chapters
2. I am able to target black space around headings <h>

If the book is 'unproperly' formatted, then it simply does not change anything.
Unproperly is inside '', because even if there are some standard about epubs, like in here https://www.w3.org/TR/epub-33/, I have so many books bought that are done 'one this way second the other way'.

I agree that there are too many barriers and options, that this cannot be done 'properly' at all. So it will be done to, say, meet 80% of books and the rest will stay the same.

culytera · 10-20-2026, 07:12 PM

Some reader apps allow editing the CSS for all books/per book. I believe Kybook and Readest have that option. They're not editing the stylesheet file itself, it's more like an even more advanced customization option.

Solitaire1 · Yesterday, 04:50 PM

One option might be to have something like a simplified CSS document loaded on the ereader, something the User can edit to specify fonts (such as "<P>="Bookman Old Style" and "<H1>=Century Gothic Bold") for the different tags. Then the User can choose to use that document for the fonts displayed rather than choosing a specific font (which would change them all for the entire document). If the User doesn't specify a font for a tag it uses the ebook's original font.

This reminds me of an issue I had with my Sony ereader (PRS-505). One of the formats it supports is RTF and I thought it would be great to use since I could just take an ebook from my word processor to my e-reader. Unfortunately, I couldn't predict which font would appear on screen. Sometimes it would a serif font, and other times it was a san serif and it was unpredictable. It would have been fine if the instructions said that RTF files will be displayed using a serif font, that would be predictable.

Solitaire1 · Yesterday, 04:53 PM

Quote:

Originally Posted by JSWolf

What are you going to do if the chapter starts with a <p>? A lot of eBooks use something like <p class="chapternumber">

Another problem comes if the chapter title has a subtitle. Sometimes the subtitle (or there text) has an h or a p.

IMHO, there seems to be too many barriers to allow editing the chapter titles cleanly.

When it comes to chapter titles and subtitles, I would think that you'd use <H1> for the title and <H2> for the subtitle.

10-20-2026, 09:48 AM	#16
petrjahoda Fanatic Posts: 596 Karma: 3774598 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	So this is how it is done as a 'beta' version. It can work as today, until 'Fonts by Style' is enabled. Then you can set it like you suggested (this goes for culytera). And it also detects other texts presented in the book, in the example text set up as times new roman (maybe some info text or what). What do you say, culytera, ok? So a normal user, like me, will not use this option. And advanced user, like you, have the ability to play with it more. Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can I just remove typeface info entirely?	awh_tokyo	Conversion	2	01-28-2013 04:03 AM
Different typeface speeds	OverTwo	Amazon Kindle	1	02-25-2011 01:38 AM
A guide to choosing a typeface	ardeegee	General Discussions	2	09-20-2010 12:51 PM
Which K3 typeface do you like best?	tomsem	Amazon Kindle	19	09-10-2010 01:01 AM
Darkness of typeface - can I adjust it?	mbelec	Sony Reader	5	02-06-2010 09:19 AM

10-20-2026, 10:57 AM	#17
mikepmiller Member Posts: 20 Karma: 10 Join Date: Sep 2026 Device: None	Wow! I know you were asking for culytera's opinion, but for what it's worth, that looks fantastic to me. Thanks!!

10-20-2026, 11:00 AM	#18
culytera Addict Posts: 215 Karma: 295686 Join Date: Jul 2021 Device: iPhone	Yeah, that looks great!

10-20-2026, 11:03 AM	#19
petrjahoda Fanatic Posts: 596 Karma: 3774598 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	OK, I will build the functionality tomorrow, this si just a design made inside the app without working code. Thank you for ideas, will be in 5.6

10-20-2026, 11:52 AM	#21
petrjahoda Fanatic Posts: 596 Karma: 3774598 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	Yes, I am aiming all <h> tags, so if this tag is used somewhere else, it will be treated the same way. But good point, I think I will be able to aim only for h tags at the start of chapter. And I will also look at those spaces. They do not bother me at all, but looks like they can bother others. Now I have no idea, what and how can be done with it, but I did not look into this yet. Thank you for it.

10-20-2026, 01:55 PM	#23
petrjahoda Fanatic Posts: 596 Karma: 3774598 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	So in the meantime I made some tests. 1. I will target headings at starts of chapters 2. I am able to target black space around headings <h> If the book is 'unproperly' formatted, then it simply does not change anything. Unproperly is inside '', because even if there are some standard about epubs, like in here https://www.w3.org/TR/epub-33/, I have so many books bought that are done 'one this way second the other way'. I agree that there are too many barriers and options, that this cannot be done 'properly' at all. So it will be done to, say, meet 80% of books and the rest will stay the same.

10-20-2026, 07:12 PM	#24
culytera Addict Posts: 215 Karma: 295686 Join Date: Jul 2021 Device: iPhone	Some reader apps allow editing the CSS for all books/per book. I believe Kybook and Readest have that option. They're not editing the stylesheet file itself, it's more like an even more advanced customization option.

Yesterday, 04:50 PM	#25
Solitaire1 Observant Owl Posts: 15,436 Karma: 70503028 Join Date: Nov 2009 Device: NookColor, Nook Glowlight 4	One option might be to have something like a simplified CSS document loaded on the ereader, something the User can edit to specify fonts (such as "<P>="Bookman Old Style" and "<H1>=Century Gothic Bold") for the different tags. Then the User can choose to use that document for the fonts displayed rather than choosing a specific font (which would change them all for the entire document). If the User doesn't specify a font for a tag it uses the ebook's original font. This reminds me of an issue I had with my Sony ereader (PRS-505). One of the formats it supports is RTF and I thought it would be great to use since I could just take an ebook from my word processor to my e-reader. Unfortunately, I couldn't predict which font would appear on screen. Sometimes it would a serif font, and other times it was a san serif and it was unpredictable. It would have been fine if the instructions said that RTF files will be displayed using a serif font, that would be predictable.