View Single Post
Old 08-12-2013, 05:40 AM   #70
ibu
Addict
ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.ibu can eat soup with a fork.
 
Posts: 264
Karma: 9246
Join Date: Feb 2010
Location: Berlin, Germany
Device: Kobo H20, iPhone 6+, Macbook Pro
@Jellby
I fully agree with your thoughts about your new example.

If all the ereaders would support to generate content via CSS I would suggest to generate the signifier "chapter" and the number via CSS in your example.

Result:
Code:
<h1>A man called <em>The Oak</em> and his <span lang="fr-FR">fiancée</span</h1>
But of course, they do not support.

My own suggestion for real life ereaders would vary slightly from yours:

Code:
<h1><span class="chapter-prefix><span class="chapter-signifier">Chapter </span><span class="chapter-number>4 </span></span>A man called <em>The Oak</em> and his <span lang="fr-FR">fiancée</span></h1>
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.
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.

Thinking about the best markup is plain fun

Last edited by ibu; 08-12-2013 at 05:43 AM.
ibu is offline   Reply With Quote