Comment #45 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Learning Manual has been taken care of with regard to this.
Thanks to Phil.
James
___
bug-lilypond mailing list
Updates:
Labels: -Priority-Medium
Comment #44 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #43 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I would expect the changes you made to -book will have fixed almost all of
these, although I've not checked. As you say, there are a few left-over,
Comment #42 on issue 1691 by reinhold...@gmail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Is this still an issue or was the problem fixed with my fix to issues 1816
and 1836?
Looking at today's LM and NR, I don't see any bars in the LM and only
Am Saturday, 20. August 2011, 06:25:26 schrieben Sie:
Comment #41 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Trevor reminded us (by email) that lilypond automatically sets
ragged-right=##t if the music is less than a
On Sat, Aug 20, 2011 at 01:18:23PM +0200, Reinhold Kainhofer wrote:
While this behavior is indirectly explained in the AU, it
does not really make sense from a user's standpoint that relative should
automatically imply ragged-right (having fragment imply ragged-right makes
sense to make it
Am Friday, 19. August 2011, 23:06:36 schrieb Trevor Daniels:
Are you sure relative=1 sets ragged-right?
That would be silly. But ragged-right is set by
LilyPond if there is only one system in the output.
This seems quite sensible.
Yes, relative=1 implies fragment, which on the other hand
Comment #36 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Request to push this change of 2.0 * %(exampleindent)s''' to 2.05 * . This
will fix all the instances of black bars where the snippet is 1 line
Comment #37 on issue 1691 by reinhold...@gmail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Actually, the problem has nothing to do with the missing quote. E.g. simply
try this trivial snippet: (which has the quote and the verbatim, and still
Comment #38 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
If [quote] is used, and the change I suggested is made, you no longer get
overfull hboxes. In book_snippets.py we have this line:
QUOTE:
Comment #39 on issue 1691 by reinhold...@gmail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Again, this would just be a workaround for a severe lilypond-book bug,
namely that it creates images that are wider than allowed.
By shrinking the
Updates:
Blockedon: 1816
Comment #40 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
The problem is not a rounding error. The first problem Reinhold identified
is detailed in issue 1816, which has a patch. We
Comment #37 on issue 1691 by reinhold...@gmail.com: Ugly bars in
PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
It's actually a very general problem of lilypond-book. The reason
why you are not seeing it with
@lilypond[verbatim,quote,relative=1] is that relative=1
Comment #41 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Trevor reminded us (by email) that lilypond automatically sets
ragged-right=##t if the music is less than a full line. This might be the
behavior Reinhold was
Comment #33 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I can break the docs in a number of ways, including using incorrect syntax
and by putting long unbreakable lines in. However, we tell people not to
Comment #34 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
The 2.05 is completely irrelevant -- it's not used at all in this example,
which still has the overflow black bars. Without using any bar numbers or
instrument
Comment #35 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I know this very well. My example pointed it out to you. If you want to
deliberately avoid the instructions in the CG, then you'll get crap output.
Comment #28 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK. Thanks. On my local system, I've changed the multiplier to 2.05
rather than 2.0, nuked build, rebuilt and the black lines where they used
to
Comment #29 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I'm not convinced that an ad-hoc solution is the way forward. Where does
the extra .05 come from? For that matter, where does the 0.4\in come
from? Is this
Comment #30 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
More generally: could you create a Tiny example (of a full .tely document,
not just
@lilypond[verbatim,quote]
\repeat unfold 100 { c'4 }
@end lilypond
) which
Comment #31 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
The 0.4\in comes from this:
QUOTE: r'''line-width = %(line-width)s - 2.0 * %(exampleindent)s''',
It's the value of exampleindent. It seems that the
QUOTE: r'''line-width = %(line-width)s - 2.0 *
%(exampleindent)s''',
It's the value of exampleindent. It seems that the rationale is
that if you subtract 2* the indent from the linewidth, then you
get a usable linewidth. Given how close this is to correct, I
was concluding the it's
Comment #32 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I can break your 2.05 solution with the following example.
The problem is that line-width is NOT the same thing as the width of the
image. Until that is
Comment #26 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK. Further updates. I started my testing today using this:
@lilypond[fragment]
\repeat unfold 100 { c'4 }
@end lilypond
I now realise that this is
Phil, you wrote Thursday, August 11, 2011 5:32 PM
I now understand this quite a bit better, and you were clearly
quite right about my previous suggestion! I think the mechanism
of reducing the line width of quoted snippets by 2 times the
indent takes off _just_ too little width - if we
Comment #27 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Excellent! You now pretty much know all I do about the situation:
- for most intents and purposes, lilypond-book has NOTHING to do with the
documentation or the
Comment #22 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I'll not be learning scheme just to fix this. If someone could explain it,
it would be a help.
I don't believe the line:
override[LINE_WIDTH] =
Comment #24 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I honestly think the simplest and best answer is just to hard code the
155mm value - it's just a magic figure that we happen to know works, so
Comment #25 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
what happens if somebody wants to make a document with usletter ? ok, it's
a totally stupid size of paper, but that's the only type I can buy in
Canada in
Comment #18 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK. The value is defined in book_snippets.py in the following way:
self.option_dict[LINE_WIDTH] = #(- paper-width \
left-margin-default
Comment #20 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
The line you found was not the main one. To understand that line, please
read the scheme tutorial in the documentation.
Keep looking for a different line in
Updates:
Owner: ---
Comment #21 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #16 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Any idea how to start looking for where the line-width is set? I've
grepped 'line-width' but the results didn't mean much to me.
Comment #17 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
oops, it's actually in python/ instead of scm/ or ly/. And to find the
relevant part, search for LINE_WIDTH in capitals.
(at least, I _think_ that's the relevant
Comment #15 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
I'd suggest leaving a bit more reserve space, i.e. using a line-width of
15.5\cm.
We will not be specifying a width inside @lilypond[options]. Instead, we
Comment #14 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK - I've done some more looking at this, following up James's work
documented in Issue 1015. FWIW, music without instrument names does not
produce
lilyp...@googlecode.com writes:
Comment #14 on issue 1691 by philehol...@googlemail.com: Ugly bars in
PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK - I've done some more looking at this, following up James's work
documented in Issue 1015. FWIW, music without
David Kastrup d...@gnu.org wrote in message
news:87pqkitzk8@fencepost.gnu.org...
lilyp...@googlecode.com writes:
Comment #14 on issue 1691 by philehol...@googlemail.com: Ugly bars in
PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
OK - I've done some more looking at
Updates:
Status:
Comment #12 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Is this blocked by issue 1015?
We've got a chain here I think and possibly a merge?
___
Updates:
Status: Accepted
Comment #13 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
What? I don't follow.
This issue cannot be resolved until issue 1015 is fixed, and that is in
turn blocked by issue 766. Some
Updates:
Labels: -Patch-review
Comment #9 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
CG edits done.
849aad2af76768b4884c6dfaaf5907c17408d6e6
Moving onto the other manuals
Comment #10 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Done some experimenting in the LM for this - see
http://code.google.com/p/lilypond/issues/detail?id=1015#c12
James
Updates:
Blockedon: 1015
Comment #11 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Owner: pkx1...@gmail.com
Comment #8 on issue 1691 by colinpkc...@gmail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Labels: -Patch-new Patch-review
Comment #7 on issue 1691 by colinpkc...@gmail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Started
Comment #5 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
@smallexample seems to work quite well for URLs, I'll go through the CG for
now and clear up as many as I can.
I also think that
Updates:
Labels: Patch-new
Comment #6 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Patch uploaded for CG
http://codereview.appspot.com/4641074
Hope its not too big. Most of it is editing Phil's 'dumping' of
Comment #3 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF
documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Just been taking a passing look at some of these. In the CG, for example,
most of the problems are caused by fixed width single lines, for stuff like
Comment #4 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
We can change @example...@end example to @smallexample...@end smallexample,
but my preference would be to split up long lines (by adding \ to the ends
of lines)
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
In the documentation build it's common to see an error message
beginning Overfull \hbox.
Comment #2 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
http://code.google.com/p/lilypond/issues/detail?id=1691
Technically I suppose that somebody could just manually tweak the line
widths of all examples which are too wide, thereby fixing this issue
without fixing issue
51 matches
Mail list logo
