Quote:
Originally Posted by wallcraft
I'm impressed that you got any text at all in-line with an image. I can't recall another example where MobiPocket did even this well. Given that Mobipocket does not float text around images, it is usually best to center the image - which MobiPocket does not do by default.
|
ha, ok. well now i know. that's rather disappointing, and another really good reason to step up the html support (why no images at all ??? that's just crazy). plus, it's completely useless if, as is the case in this book, you have illuminated first capitals at the start of each chapter.
Quote:
Originally Posted by delphidb96
Yep. Bookeen hasn't quite got all the bugs out of its HTML handling. And I've learned to live with the quirks of .mobi on Cybook vs .mobi on the PC - which one would presume did not need to happen given that Bookeen should be working from the Mobipocket SDK. 
Derek |
yes, there is still some work to do on html handling, but some of the html strangeness comes from mobipocket as well ; for example, the rss feeds it picks up, apparently don't include any images. that seems strange to me. and when creating a .prc book from html, clearly there are some things i have not understood yet...
Quote:
Originally Posted by Ralph Sir Edward
Precisely. My apologies for not being fully descriptive...
|
that's what i thought you meant, it was pretty clear, but i did notice in the menu you could make all the text bold so i thought i should be sure it wasn't something like that, and i just hadn't noticed that function.
Quote:
Originally Posted by wallcraft
Is the encoding set correctly in the .opf and .html files (and therefore in the .prc)? It should probably be utf-8. I think MobiPocket also does some in-line translation of (mis-coded?) special characters in the Desktop Reader, because I have seen some cases where FBReader gives squares but MobiPocket does not. I can't recall if this was fixable in FBReader by changing the encoding or not.
Another issue is that Desktop MR will override your font choice if it has to in order to get all the ranges of UTF-8 it needs. FBReader only uses one font at a time (exactly the one you select), so it may be a better test for what will happen on the Gen3. A free font with good coverage (but not to everyones taste) is Deja Vu Sans. |
ok, i will have to check all that information !! i don't have fbreader, so i'll have to find that and install it to test with.
as for the encoding though, i would think yes it is correctly encoded, since if it were a question of incorrect encoding, the characters should have been missing in the desktop reader also, right ? but they display fine there, they are only missing when i look at the book on the cybook.
anyway i'll check out Deja vu sans, but for the body of the text i prefer a serif font, do you have a recommendation for that ? i honestly like georgia quite well and use it myself frequently, so it's not too important unless there is a different one with more characters available.
thanks everybody for all your help !! i'm trying to explore as much as possible in such a short time and it's great to benefit from your experience !!