View Single Post
Old 11-19-2017, 07:58 PM   #287
jgoguen
Generally Awesome Person
jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.
 
Posts: 1,061
Karma: 2178845
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
The only thing that looks even possibly relevant is the KePub has both xml:lang="fr" and lang="fr" set on the top-level <html> element; the ePub only sets xml:lang="fr". But my understanding is this is supposed to be allowed since "lang" is a built-in property of the <html> element and "xml:lang" is added by the inclusion of xmlns="http://www.w3.org/1999/xhtml", and either should be sufficient to override the interface language. And in the KePub content.opf also sets the language, but again as I understand it the per-file language that's set should override that.

Though, in the Unicode world that applies (or should apply!) because the XML encoding and Content-Type element are set to UTF-8, the interface language should only matter for the app to choose what translation to use for displayed app strings. 0x65 and 0x202F are the same Unicode character no matter what language you're using. Assuming your font supports it. Though it's weird it apparently falls back to a different font in some cases and not in others. And there's no font family specified, except for one specific class that isn't applicable here sets the font family to "WINGDINGS".
jgoguen is offline   Reply With Quote