Thread: Typos in ebooks
View Single Post
Old 05-20-2011, 01:26 PM   #197
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 7,556
Karma: 19500001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by raac View Post
Still, if there is a unicode compatibility issue I don't see why publishers can't use the ASCII character codes so we don't have this problem.
The problem is not the encoding of the book, it is the lack of an appropriate glyph in whatever font is used.

What do you mean with "ASCII character codes"? I guess it's one of these:

1) Use named or numerical entities instead of the Unicode character. For instance, instead of "Peņa" write "Peña". This does not solve anything, no matter whether you use "ņ" or "ñ", the font does not have the character, and it shows a box or a question mark instead.

2) "Downgrade" to some similar character that is in the ASCII set, removing diacritics etc. For instance, instead of "Peņa" write "Pena". This risks to be completely wrong and misleading, "peņa" means rock, boulder, while "pena" means pain, sorrow. There's a reason why diacritics exist in most languages.
Jellby is offline   Reply With Quote