Quote:
Originally Posted by Jellby
I'm sorry, but that code is wrong. You are using a font with non-standard mapping, and then some symbol codes for different characters. This is disallowed by the ePub spec:
"Fonts must not provide mappings for Unicode characters that would change the semantics of the text (e.g. mapping the letter "A" to a biohazard symbol)"
|
Well, that's depressing -- very seriously so. My ebook works just fine (in iBooks), and everything validates just fine, so who checks these things and, indeed, then disallows them? Apple states, for example, that any book uploaded for sale on their store "must" validate, and yet they have an ebook up for sale there -- about how to design ebooks, no less! -- that's chock full of errors and invalidations.
Quote:
The long-s has its own Unicode spot, and ligatures should be dealt with by the font, not by using specific characters in the input. You should write:
Thou appereſt in my thouwts ſo often...
and use a font with ſ glyph and proper ſt and ft ligatures. Then you won't need those "nowrap" spans (as long as the reader understand that ſ is a letter)
|
Well, the thing is that in order to do this with an embedded font, the font has to be freeware, of course -- this JSL font set is the only one that I know of like that.
Apart from that, though, if what you're saying above is true, then wouldn't that mean that one can't use any "alt" or "supp" or "exp" fonts embedded in one's epub? I'm thinking, for example, of Adobe Caslon (among countless, countless others). If you wanted to use the "ct" ligature, found in Adobe Caslon Alt Regular, you specify that font and use the "c" character.
And re words breaking at the end of lines...
Quote:
which, of course, was common in 16th century typesetting 
|
Yes, but they would have a hyphen then -- when my "olde" words break because of those special characters, the two halves are treated as separate words, and no hyphen is inserted. :/