Re: All done except for unitelligent line spacing issues

[Selma Leathem]

Let me know what you think before I do it. If I put breaks between sections there might be a bit more white space than inserting page breaks to eliminate white space all together. But it still  would look ok.

 

I'll send  a version that has all the chapters  together shortly.

From: Selma Leathem <address@hidden>
To: John Darrington <address@hidden>
Cc: Ben Pfaff <address@hidden>; "address@hidden" <address@hidden>
Sent: Monday, October 8, 2012 7:39 AM
Subject: Re: All done except for unitelligent line spacing issues

One way to deal with manual page breaks being user freindly for changes in the future might be to put them after each sub or longish subsub section. The layout wouldn't be as nice as this way, but still much better than texinfo's default spacing.

 

 

From: John Darrington <address@hidden>
To: Selma Leathem <address@hidden>
Cc: John Darrington <address@hidden>; Ben Pfaff <address@hidden>
Sent: Monday, October 8, 2012 12:24 AM
Subject: Re: All done except for unitelligent line spacing issues

On Sun, Oct 07, 2012 at 03:36:41PM -0700, Selma Leathem wrote:
    The texinfo help forum recommended I clean up the space issues with page breaks. It does make it look much better, but would make it a bit harder for future revisions. I'm assuming that any revisions would be minor enough for this to not be too much of a consideration.
    ?
    It looks great in html, and I get the feeling texinfo was not meant for image heavy documents in pdf, so take your pick an ugly pdf or an ugly code. I personally feel it wouldn't be too hard to work around the page breaks, only an extra 5 min of your time.

You're right.  Adding manual page breaks makes maintenence harder, but is sometimes necessary.
For this reason it's normally done as the last thing just before a release.

At any rate, in this case, it should certainly be done after the chapter has been incorporated into
the manual, since doing that has the potential to change where the page breaks should go.

Regards,

John

--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://keys.gnupg.net or any PGP keyserver for public key.