On Thu, Jun 23, 2011 at 06:48:47AM -0600, Colin Campbell wrote:
> On 11-06-23 05:46 AM, Graham Percival wrote:
> >On Wed, Jun 22, 2011 at 06:52:43PM -0600, Colin Campbell wrote:
> >>On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
> >>>I would start with this:
> >Looks great; Colin, could you add that to the CG in the Issues
> >chapter?
>
> That's Dmytro's script, Graham! My bash-fu is still at an early stage.
Ah, sorry, my punctuation was too confusing.
Dmytro: looks great.
Colin: add this to the CG (since Dmytro isn't trained in making
patches).
> > Most bug reports are short and don't have a tagline
> >defined, so you want to trim the existing one. If a bug report
> >explicitly adds a tagline="abcd", then it would be good to not
> >trim that one. (if the tagline= is not relevant to the bug, then
> >the bug report should be rejected because it's not Tiny)
>
> A problem arises when, as I suspect, the default behaviour is
> tagline = ##t, even when not explicitly stated in the \header block.
> IOW, the absence of "tagline = " doesn't mean absence of a tagline.
> The presence of the tagline means convert must include the entire
> page in the trimmed area, which defeats the purpose of the trim.
I suspect that you're confusing yourself, or at least certainly
me? The script produces a small png for:
\relative c' { c4 }
That's what we want. Do you see a large png for a Tiny example?
If so, please give the Tiny example which causes the large png, so
that we can fix that.
As far as I know, any example containing an explicit
\header{ tagline =
either requires the tagline to be present to demonstrate the bug,
or else the example is not Tiny.
This is for the bug squad, not random users. Screw the users; I
only care about volunteers. :) If you're interested in
improving things for random users, great, but that's a separate
issue from the helping-the-bug-squad work.
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
