From: Colin Campbell Date: Mon, 4 Jul 2011 18:58:02 +0000 (-0600) Subject: CG: adds trimpng script to sect 8.5 X-Git-Tag: release/2.15.5-1~21^2~3 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=8824646423fbe78d8259a02b4e56064fe2abc8bb;p=lilypond.git CG: adds trimpng script to sect 8.5 Added reference to trimpng.sh in CG 8.5 Adding Issues --- diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi index 46840db674..56b97d38be 100644 --- a/Documentation/contributor/issues.itexi +++ b/Documentation/contributor/issues.itexi @@ -78,8 +78,8 @@ Sign in to google code by clicking in the top-right corner of: @uref{http://code.google.com/p/lilypond/issues/list} @end example -You cannot log if you have Google Sharing -@uref{http://www.googlesharing.net/} enabled. +You cannot log on if you have Google Sharing enabled +@uref{http://www.googlesharing.net/}. @item Go to your @qq{Profile}, and select @qq{Settings}. @@ -681,6 +681,15 @@ If the issue requires one or two pages of output, then generate a lilypond --png bug.ly @end example +@item +Images created as @file{bug.png} may be trimmed to a minimum size +by using the @code{trimtagline.sh} script, which can be found at +@uref{https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.sh} + +@example +trimtagline.sh bug.ly +@end example + @item If the issue cannot be shown with less than three pages, then generate a @file{bug.pdf} file with: