in fact, I've been fighting with Nisus Writer pdf/html renditions since 2007, even though year after year, problems have been ironed out one by one...
now there are only a few issues left — mainly the rendition of those link-back
files, made with OmniGraffle
, and dragged directly into the Nisus Writer text window: these are vector
graphics which will eventually be converted to jpeg files with a very very
unfortunately, the texts I write are (1) abundantly illustrated, and (2) supposed to undergo constant evolution, reflecting my students' feedback:
- each week or so, the modified text must be made available on-line, both as pdf and in html format...
- it means that a given text file will be revised and republished several dozens times a year!
if quality output can't be obtained in both formats in a fully automated way — as when using LATEX
— then it's going to be a real pain, because there's only one way to prevent Nisus Writer from exporting the graphics to low-res jpeg
these days, and that's substituting, in the source file, the original vector
graphics for cheap 72-ppi bitmap renditions...
so this is a trade-off, sort of: either it'll yield a top-notch pdf version with unusable html sh!t, or I'll get a pdf that won't print nicely but the html's graphics will at least be intelligible!
now I've found another [painful] way to get the best of both worlds: once the text has been exported to html, I would patch each href manually
to get rid of the low-res jpeg file, and point to a new 300 dpi png file...
I don't know how other people manage to produce high-quality output that doesn't depend on the format, but from the programmer's vantage point, this needs not be much convoluted:
- either the graphics are already in bitmap format…
leave them alone
if some fool didn't really know what he was doing when he embedded a 1000x1000 image, then let him have it his way
- or they are vector graphics…
then they should be exported to 300-dpi png format — but scaled down to 25 % to display as 75 dpi
okay: the intended scaling and resolution may vary, and this, obviously, should be adjustable as a user's preference
— and that's exactly what I thought was your final conclusion some 3 years ago!