In the PDF on pp. 164, 166, 167, 168, 169, 179, and maybe others seem to show a black bar at spot(s) on the right side and don't always seems to fit in the page where that happens. I noticed during make-web that messages scrolled by such as:
Underfull \hbox (badness 10000) in paragraph at lines 564--567 [EMAIL PROTECTED] Emacs. Emacs is an ex-ten-si-ble text-editor. It is avail-able from Underfull \hbox (badness 4699) in paragraph at lines 564--567 @texttt http://www.gnu.org/software/emacs/[EMAIL PROTECTED] . You need ver-sion 21 to use col- Underfull \hbox (badness 4673) in paragraph at lines 580--582 and (many more than I list here) Overfull \hbox (20.13745pt too wide) in paragraph at lines 146--280 [][] | Overfull \hbox (20.13745pt too wide) in paragraph at lines 282--400 [][] | Overfull \hbox (20.13745pt too wide) in paragraph at lines 402--503 [][] | There seem to be other messages that scroll by during the make web process that report some warnings such as (but not limited to) 'junking lyrical event' and a number of messages containing 'programming error' are scattered about. I figure some messages probably do come out when making the documentation since tips & tricks + regression tests does a lot of strange stuff, but in make and make web, I'm guessing there are a few that are unnecessary. Seems my make web troubles may be down to netpbm again; /usr/local/netpbm/bin/pnmtopng was needed, but not in my path. Wether or not that is preferred, that was the default install location my source compile of netpbm went to. I now just append it to my path prior to building when necessary. I upgraded gs, with no luck. Odds are it wasn't the culprit. Probably some old fonts that I've finally gotten cleaned up right were the problem. At this point, I finally have make web running successfully. Are there times that I can get away without make clean type steps after a cvs upgrade? I usually do it after every update, but I thought that wasn't always necessary. Are there rss feeds about lilypond available? These could be useful to notify about lilypond updates, which could then help keep people up to date and maybe even be used to automate package updates. I'll have to see if maybe I can help with package providing next... Thanks again, Ed Sutton _______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
