![]() My general workflow, if I could find the right program that just works, is Markdown -> ePub. It's best to keep PDF for fixed format output, such as printing, or getting someone to sign a document. Although an open format it seems that you can never be sure how a 3rd party's processor is going to parse from PDF to another format. I hate having to click a link to see a footnote when the eReader should be able to work out when to display a footnote at the bottom of the relevant page - as this can be done in HTML, I don't know why it seems to be such a chore. mobi is the poor support of some standard hard copy features, such as footnotes and side-bars. ![]() It's annoying that a document written with Body Text, Header 1, Header 2, Header 3, and a style for Code, can be output with all manner of extraneous and needless style/class/id tags. Images, and even video to some small extent, is supported.ĮPub can also be a reasonably "clean" format, with minimal useless markup cluttering up the file and introducing errors into converted documents, although your mileage will vary with different software that outputs ePub. You can style the internal HTML, all fancy if you wish for display on the web, or do minimal styling for use in eReaders. When it comes to novels, with perhaps minor images in chapter headers or small images in the text, the best format to output to is ePub as it's so versatile and easily converted to something else. The best format for any eReader is the native one. mobi, and ePub formats because the font type is set by the reader's device. Font family and most font settings are irrelevant to Kindle's.
0 Comments
Leave a Reply. |