”is the epub working?” poll

[silviolorusso]

Hello everybody,

I'd like to ask to check this epub, in order to understand if there are errors or such things.

Please add device and reading platform.


Thanks!

[Hoyt Clagwell]

Tried it on my Nook STR and Sony 650. For me the text was way to small and it would not let me adjust the size of the font. I used Calibre and reconverted it to ePub and then was able to adjust the font size.

[silviolorusso]

Thank you very much Hoyt! I think I will totally delete the "font-size" in the .css

[pholy]

Instead of eliminating the font-sizes, change them to a relative measure like em - 1em for the body. 1.15em or 1.2em for the title and subtitle, and 0.6em for the colophon. This will allow the readers to change the font sizes while preserving the look of the different sizes used.

In general, relative units are a better choice for fonts and indents, but absolute sizes work best for margins - but that's my opinion, I'm sure others may disagree.

[silviolorusso]

Great pholy! I actually didn't know about "em".

Thank you

[Jellby]

Or you could use percents: nothing for the body, 115% or 120% for the titles, 60% for the colophon.

[DaleDe]

Originally Posted by Jellby

Or you could use percents: nothing for the body, 115% or 120% for the titles, 60% for the colophon.

I have found that 1em is better than nothing, particularly when the font size changes within a paragraph using a span. Having a defined size is better than the default which can be a default inherit depending on the reader resulting in the size remaining changed after the span is done until the paragraph end. I have adopted 1em for that reason if there is a need for any changes to the default size. Of course defaults for h2, h1, h3 etc. are change sizes already as they have different defaults.

[Jellby]

Originally Posted by DaleDe

I have found that 1em is better than nothing, particularly when the font size changes within a paragraph using a span. Having a defined size is better than the default which can be a default inherit depending on the reader resulting in the size remaining changed after the span is done until the paragraph end.

Do you mean this:

<p>Some paragraph with <span class="large">large words</large> as a sample

would look different with this style:

p { font-size: 1em; }
span.large { font-size: 200%; }

and this:

p { }
span.large { font-size: 200%; }

(which would display "as a sample" in large font too)?

If that's the case, it must be a bug in whatever reader does that, or there's something I've still not grasped from the CSS spec.

[DaleDe]

Originally Posted by Jellby

Do you mean this:

<p>Some paragraph with <span class="large">large words</large> as a sample

would look different with this style:

p { font-size: 1em; }
span.large { font-size: 200%; }

and this:

p { }
span.large { font-size: 200%; }

(which would display "as a sample" in large font too)?

If that's the case, it must be a bug in whatever reader does that, or there's something I've still not grasped from the CSS spec.

Yes, it was a Hanlin V3+ using ADE software. It seemed to interpret that lack of a specific fontsize as inherit the previously set size within the block. It is likely a bug but then older eBook readers seem to be stuck with what ADE version first appeared on them. Although I am not sure exactly how inherit is supposed to work.

Dale

[JSWolf]

Originally Posted by Jellby

Do you mean this:

<p>Some paragraph with <span class="large">large words</large> as a sample

SHould actually be...

<p>Some paragraph with <span class="large">large words</span> as a sample