Quote:
Originally Posted by JSWolf
One thing you should never ever do is replace a different character with the alternates and use that. Some programs/devices allow the embedded font to be replaced or not used.
|
It's not a different character, it's an alternate form.
It's not like some of those dingbat/foreign fonts that replaced "abcd" with absolutely different symbols "αβγδ".
It's substituting a swashy 'Q' with a normal 'Q'. Or 'a' with a more rounded 'a' (as a child would write [see GIF below]):
https://helpx.adobe.com/content/dam/...n-type-bar.gif
https://helpx.adobe.com/illustrator/...haracters.html
Before:
https://ilovetypography.com/OpenType/_img/salt_src.gif
After:
https://ilovetypography.com/OpenType/_img/salt_trgt.gif
I would agree with Doitsu, your best best would probably be to flip the alternate symbol in the font itself, then embed that modified font into the Fixed Format Ebook. Currently, that advanced CSS3 is just not well supported across readers/browsers.
Side Note: If you look at the font OP mentioned, the 'v' looks a lot like a 'u', and in a children's book, I could see how that would be extremely confusing.
Quote:
Originally Posted by momoha
[...] which solves my problem at the moment, but not for potentiel future cases where a book would be using both glyphs, regular and alternate.
|
I can't think off the top of my head where you would require both... besides Maths. Are you thinking of things like the swashy Q, where it only applies in the beginning of a word? Or in special ligatures like "Qu"?
Anyway, it all stems back to a problem of reader support:
- Embedded fonts are already an issue
- Can't guarantee device supports even that.
- Advanced CSS3 support is nearly non-existent in ebooks
- If it's not supported in browsers, there's 99.9% chance it won't work in books.
- and Fixed Format is just a plain disaster.
If you created a book which relied on alternate characters for comprehension, you most likely have serious underlying issues in your text.