Quote:
Originally Posted by hobnail
We kind of went through this in the early days of the web, when web page designers were people with a print background; Pagemaker, Indesign, Quark, etc. and, for an example, they kept trying to get a fixed layout like they could with a printed page. Who can forget page layouts that used tables or spacing with zero width gifs?
|
Idiot Web designers STILL do that. Stupid sites that need a desktop & Mobile version, or on desktop you have to change browser window size.
I format for ebook first & then when final proof is done then Save-As with the page size in the name and format the paper versions. My websites work on 4.3" phone to 2K 24" with a single version. Make desktop browser window phone number of pixels and it's the same as on the phone. Use a 10" to 14" Android HD tablet and it looks like desktop, you don't get a stupid mobile version like most "leading" websites serve.
Headers, footers, notes, footnotes, contents, index/concordance, images, page numbers, spacing/margins etc are all different for paper. I tried both workflows. I started with work flow for paper as I had decades of experience producing and training. Considered HTML workflow for a while as input to Mobi Creator but a docx Save As with styles, headings etc for epub works best. Easy to adapt final version for paper. All proofs & annotation now on eink via epub & Calibre. The proof for paper is only about changed and extra content.