From: Allin C. <cot...@wf...> - 2011-03-01 02:51:48
|
On Mon, 28 Feb 2011, Mojca Miklavec wrote: > On Mon, Feb 28, 2011 at 17:27, Ethan Merritt wrote: > > So - what's wrong with the document produced by your system using > > the current "make pdffigures" target? How is it different from > > the pre-prepared one in the distribution? > > I need to find the pre-prepared one first to compare. But see the > attachment for a single example (there are many others). Some figures > are fine, but many of them are weird. They: > > - overlap with one another (if two figures are close to each other, > the second one will just overlap the first one) > - destroy height of footer (text goes way too low into footer) > - floats take space on next page (where they don't even show up) > - it happens that title stays on previous page and paragraph with > figure starts on next page > - if there is some verbatim code, it overlaps with the figure (see attachment) I think you're exaggerating. Having just done "make pdffigures" on the CVS source I see two cases where text spills onto a figure, one case where one figure is partly occluded by another, and zero cases where a float takes ghost space on the following page. I do see several cases of orphaned headings for plotting styles. And the footer looks too small for typographical balance, though that presents a trade-off with keeping the file compact. The problem with the (few) cases where a figure is partly overwritten seems to be that picins defines the effective height of a "parpic" paragraph by the typeset height of the text. If part of a figure sticks down below the text it has to fend for itself and will get clobbered by anything that sticks out far enough to the right in the next unit of stuff on the vertical stack. In typestting complex material with (any variety of) TeX it's often necessary to make a few tweaks to get things just right. In this case judicious insertion of \vspace would help. Unfortunately this is not easy when the TeX is machine-generated. Allin Cottrell |