Updates:
Status: Verified
Comment #13 on issue 413 by brownian.box: PNG image is offset an therefore
cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Fixed
Labels: fixed_2_13_29
Comment #12 on issue 413 by pnorcks: PNG image is offset an therefore
cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
This issue should be fixed.
To test, copy the example from comment 10 into a file named
Updates:
Status: Started
Owner: pnorcks
Comment #11 on issue 413 by pnorcks: PNG image is offset an therefore
cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
(No comment was entered for this change.)
___
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #10 by paconet.org:
#268 (preview) is fixed, #413 (default PNG) is not.
LANDSCAPE:
\version 2.11.55
\header { title = 229 composer = Composer Composer }
{ c'' }
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #9 by hanwenn:
Hi, #268 was extremely thin slices that went missing at the end. Can
you check if
.55 fixes the issue for you?
thanks.
--
You received this message
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #6 by v.villenave:
I can reproduce it with 2.11.48, so I guess it's still valid.
Issue attribute updates:
Status: Accepted
--
You received this message because
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #7 by gpermus:
I think Han-Wen wants a minimal example. I certainly know that the
attached .ly is
not minimal.
--
You received this message because you are listed in
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #8 by hanwenn:
no, for this it doesn't make a difference.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #5 by hanwenn:
marking invalid, since we have no feedback
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #3 by gpermus:
possible dupe of 268. (I recommend fixing 268, then see if that fixes this one)
--
You received this message because you are listed in the owner
or CC
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #2 by vaclav.kocian:
Well, here is a batch, which I use:
1 #!/bin/sh
2
3 FILE=$( find . -name *.ly )
4 NAME=${FILE%.ly}
5 lilypond --png --pdf $FILE || read foo
Apropos, I
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #1 by hanwenn:
Please detail cmd line options used, and provide a simple example file.
--
You received this message because you are listed in the owner
or CC fields of
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
New issue report by vaclav.kocian:
While PDF works very fine, every PNG image generated by lilypond is offset
a little towards the end of staff, therefore score is not displayed in
13 matches
Mail list logo
