Quote:
Originally Posted by ibu
If the ereader would be able to generate content via CSS I would suggest to generate the term "chapter" and the number via CSS in your example.
|
Indeed, but counters are out of the ePub 2.0.1 spec. And if you want to use the full "Chapter # <Title>" in the TOC, having that explicitly written makes it easier to generate the TOC with Sigil, for instance. Anyway, this was only an example of how things could be, not optimized by any means, don't take it to the letter
Quote:
I would omit the span around "A man called The Oak and his fiancée".
And I would enclose the spaces behind "chapter-prefix" and "chapter-number" in the span, to beware the option to fade it out completely with CSS, if the layouter wishes that.
|
Fair enough, different approaches with the <span>ning, and agree about the spaces, I intended to mention that you should be careful with spaces if you are planning on hiding content.
Quote:
And a very sophisticated tiny thing:
May be it's good to declare the language more detailed, because there are several regions, where they speak French.
|
But I don't think it makes a difference in this case, especially since it's a standard French word imported into English (some might even argue that it should not be italicized at all). If we don't have any further hint of the specific variant the word belongs to, I think it's better to keep it generic with "fr", even if we know the author is from Montréal, "The Oak" from Brussels and the girl from Geneva
