@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