Quote:
Originally Posted by Faterson
I just don't get why it should be so important for Marvin to immediately show the ideal font size (when every reader believes something else to be ideal!) upon the first opening of a book.  I mean, why do we have all the fantastic formatting buttons in Marvin? Anyone can just push a few buttons, and there it is -- the ideal layout, and it remains sticky.
As to "MS Word styles", they are notorious for being a disaster. MS Word may be the world champion in producing inefficient, bloated code. I would not be surprised if any EPUB created in Word, out of all software packages, would fail to display as expected; I would be surprised if it did.
Does your code get validated in the w3c.org validator, Wyndham? In the EPUBs I create, I avoid anything but absolutely necessary code, so any MS Word styles are out of the question. I especially avoid specifying any font sizes, other than relative ones for (mostly) headings, and so, the e-books then look very nice in Marvin not just to me, but to any reader whose reading preferences may be very different from mine.
Specifying font sizes (other than relative ones) should not be a matter for the e-book code to handle -- it should be left up to the e-book reader (such as Marvin) to handle, and Marvin handles it beautifully. |
Why do you have to be so offensive? I was trying to be helpful by reporting problems and supplying some information to hopefully help solve the problem. I am thinking I may avoid these discussions altogether is this is going to be the response.
I have never asked for the ideal font size, so to put that in your reply is making something up and quite frankly missing the point.
Until the most recent update, the fonts WERE NOT STICKY. If they were, then Kris would not have made an update and then stated this was one of the changes in the update.
MS Word Styles are excellent for formatting a Word document and should be the ONLY way a Word document is formatted. I did not say anything about generating an html file with Word, which does generate desperately bad html code. As bad as this code is, it becomes infinitely worse if a mixture of formatting is used rather than just Styles.
I use LibreOffice to generate an html file (from the MS Word document) and then use Notepad to remove unwanted code, leaving a clean html file which is then imported into Calibre. I have validated the code, although I don't do so every time.
I have not yet tried the new option in Calibre to generate ePubs directly from MS Word documents, so can't comment on how successful that would be.
All of this however is getting off the point, which was that the ePubs I generate have consistent formatting and I would prefer them to look the same in my eBook reader. Marvin was not doing this, but it now is since the latest update. The font sizes are now sticky, which they were not before.