I would assume PG must be doing something like this now for html files forereaders. If you know an html file is going to an ereader format, and you know
the default css has, say, irrational margins, you adjust the css. It's what css is for.
Isn't that currently happening? Especially for DP books, the pseudo-standard
css would I'm sure have default adjustments that would work in most cases.
Or am I missing something?
On Mon, Feb 6, 2012 at 1:24 PM, Lee Passey
<lee@novomail.net> wrote:
On Mon, February 6, 2012 12:14 pm, Jim Adcock wrote:
> Mapping what you are saying to the HTML world, what you are saying is that
> instead of including the CSS inline in the markup HTML file, we should have
> that CSS separated into a separate CSS file, and if we needed to target very
> small machines, or EPUB machines, or MOBI machines then we could just have
> separate CSS files for those machines, or just do pragmatic marking of some
> small regions of those CSS files using @media statements and queries so we
> don't actually even have to create a separate CSS file for each major class
> of machine.
If I have correctly understood this terribly run-on sentence...
yes.