[QUOTE=Psymon;2667963]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?[quote]
There's no way to automatically check this.
Quote:
|
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.
|
I'm sure there are a few freely embeddable fonts with long-s and ligatures.
Quote:
|
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.
|
It depends on what you mean with "can't". It certainly means that it's against the specification, and for a very good reason: the text is garbled without the embedded font. And you just cannot assume that the embedded font will work at all, because:
- A user may disable them.
- A reader may not support them (or the specific format/version you are using).
- A medium may not use fonts at all (think text-to-speech)
and it would break searching too, I'd have to search "acion" if I want to find "action".
But there's probably an OpenType Caslon font with a proper "ct" ligature that appears (maybe optionally) whenever there is a c + t in the text... that's what one should use.
Quote:
|
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. :/
|
Actually, I meant that old books used to break words without a hyphen or any other sign.