View Single Post
Old 04-05-2010, 09:22 AM   #8
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 65,008
Karma: 43118253
Join Date: Nov 2006
Location: UK
Device: Kindle Voyage, iPad Mini, iPhone 4, MS Surface Pro, N7
Quote:
Originally Posted by paulpeer View Post
Not only the metadata cannot be read. The main problem is the table of contents of the device: imagine you have a reader with 50 books in Tamil, or Hindi). In the TOC you'll see a beautiful list of 50 rows of question marks. If you want to open a certain book, you will have to try them all and hope the one you are looking for isn't the 50th ...
There are two different things being discussed here:

1. The table of contents of the book. This will indeed use the device font which may or may not support the appropriate characters. A way around this is to have an "internal" TOC in the book itself, implemented with hyperlinks.

2. The list of books on the device - ie the "library". This may display metadata from the book or it may simply display the filename, depending on the device.
HarryT is offline   Reply With Quote