Quote:
Originally Posted by jbenny
If you look around on the ETI site, they have a list of all the extended characters supported by their readers. I used to have a copy, but can't seem to find it.
|
thanks for that info, i will try to find it, it interests me.
@ nrapallo : well, since i made every other possible version of this book already, why not mobi too ? if only for the sake of science...
so i installed MobiPocket Creator and first i tried making a book from the html, then from the word files.
there are 2 separate problems with this particular file :
1. the unsupported glyphs. only possible solution (barring an update to the imp firmware and eBook Publisher programme from ETI, which i am hoping for but hardly seems likely to appear tomorrow, or me buying a Gen3 *especially* to read this book...) : make images. not feeling zealous enough to do that today.
2. the inexplicable messed-up text formatting and page layout. this is clearly a problem from *somewhere* in the css, because if i remove the css file and build an imp (in eBook Publisher), the text reverts to default of left-aligned, no bold, etc. *however* i still have not figured out where, because the css file (which is REALLY long) does not seem to contain the corresponding rules (text align right, huge left margin, etc. ; when i search for these rules in the css, they only appear on classes which are not actually used anywhere in the document, and the classes applied to the text have the right rules).
so, back to my trials (and tribulations
) when i put the html file through MobiPocket creator, i wasn't sure how to attach the css file, and it turns out it is not imported automatically (first time using MPC : it was quite easy, but i imagine there are some details i don't understand). the glyphs are supported in mobi files, however without the css file there was no formatting at *all*, so the book was not very nice to look at. i didn't bother to make an imp there, because i knew the result would be the same as when i tried to make an imp directly from the html without css.
then i tried using the doc file, which was formatted (it was the original html file, opened in word, and saved as .doc, with some reformatting done by me afterwards, notably to remove the rather surprising page breaks after every paragraph return).
this file of course gave much better results, about the same as when i made the imp directly from the doc file, although i lost some features which i like in imp (how do you make a running header in mobi ? also, how do you specify a serif font for the body text ?).
Conclusion of the experiment : using mobipocket creator as an intermediate version only adds additional steps to the conversion, with no apparent improvement, and in fact loss of some features (header, serif font). however, making a mobi file as the *destination* file is an improvement over the equivalent imp file in this case, in that the mobi format correctly supports the special characters.
Conclusion part 2 : experimentation overall inconclusive, as i still don't understand why this blasted file interprets the css in this ridiculous manner (especially since firefox can interpret it perfectly, and word interprets it with also some strange things but not the SAME strange things). it is the second time it has happened to me on a drm lit book (2 out of a total of 4 books converted... not a very good score...), and *never* on a non-drm conversion from mobi format or creation from zero of a PG text. it is really infuriating and i will definitely hesitate before buying another drm book.