Lee>If you were to follow these rules you would have exactly what you are asking for: a single HTML file that would satisfy all three purposes. If *I* were to follow these rules I would produce the same HTML input to PG as I am already doing 99% of the time. I will admit that on the last day or two before shipping I am willing to compromise and "tweak" locally what goes out to fix any small remaining problems without taking the risk of wholesale damage to what I have already SR'ed two or three times before. The problem is with the great mess of other posters, and with a PG/DP mentality which says every last comma is important, but producing books that real customers can actually read on their real devices is not important. One misplaced comma is important, but literally 1000 formatting errors in one file doesn't count, because "We" don't care. With this caveat: I do not use external CSS files because PG doesn't accept them. And I am happy to put a couple lines into my CSS in order that the same HTML will render "correctly", and more or less consistently, on HTML, EPUB, MOBI, and KF8 devices. Agreed that I personally would probably rather see external CSS files.