lucy24 - 9:27 am on Dec 10, 2011 (gmt 0)
I mean filesize in kilobytes. Like this (reading the numbers off my HD):
Original html file: 156K plus a few K of external stylesheet.
created by Safari 389K
created by Opera 946K
Firefox and Camino, both 1.1MB
Chrome 2.2MB (!)
They all look the same except that only Safari and Opera show the background colors of table cells-- but this may have been my fault for forgetting to change a default.
I also have versions made by TextEdit, either directly or via Safari, but these got horribly mixed-up in the horizontal alignment. (It's a series of grammatical tables.) Conversely, both Opera and the Mozillas got confused and ate part of the Index, which is in three columns. I may be able to fix this by using more redundancy in the CSS.
The visual size is based on display in the browser that created the PDF. So Opera's version comes out a little smaller (in display size and hence pagecount) because it won't let me set a 15pt font size so it's at 14.
It is probably not surprising that Safari does the best job, since it's the most intimately connected with the OS.
Mac-generated PDFs are fully searchable-- at least in Roman type-- but they do not preserve internal links (# fragments), only complete links in http://