Comment #7 on issue 934 by percival.music.ca: GUB doesn't include Japanese
fonts
http://code.google.com/p/lilypond/issues/detail?id=934
Running lilypond from the command-line works with utf-8.ly. But now I
remember that
the builder sets up its own environment and clears everything but a fe
On Fri, 19 Mar 2010 13:39:36 -0700, Joe Neeman wrote:
The begin_of_line_extent should be zero
> for lyrics, which should allow the lines to be close together in the
> height-estimation procedure.
The difficulty of debugging this, is how do I tell which grob is
which. They are Scheme poi
On Fri, Mar 19, 2010 at 1:56 PM, Graham Percival
wrote:
> It's been a few days since 2.13.16 was released. Have all bug
> squad members checked the regtest comparison?
>
> I ask because I wrote down a list of 3 regtests that looked broken
> to me before releasing 2.13.16, but I thought this would
On 3/19/10 8:40 AM, "Phil Holmes" wrote:
> According to the documentation for 2.12.3 "There is no support for chords
> where the same note occurs with different accidentals in the same chord." I
> have a situation where this is required and would like to add it as an
> enhancement request.
I've
Hi Joe,
Thanks for the tips, and have a nice and safe trip!
> The estimated height for the whole system _should_ take into account the
> fact that the lyrics can be squeezed between the systems. Have a look at
> the comment in align-interface.cc:104 (which should get called as a
> result
It's been a few days since 2.13.16 was released. Have all bug
squad members checked the regtest comparison?
I ask because I wrote down a list of 3 regtests that looked broken
to me before releasing 2.13.16, but I thought this would be a nice
test. :)
Remember, I'm not at all likely to remember
Unfortunately, I'm about to go out of town for the weekend, so I don't
have time right now to follow this up properly. But I've left a couple
of hints below.
On Fri, 2010-03-19 at 11:05 -0400, Boris Shingarov wrote:
> On Wed, 13 Jan 2010 19:37:14 1100, Joe Neeman wrote:
>
> > It's nice to see
Here are the two illustrative examples.
On Fri, 19 Mar 2010 11:05:30 -0400, Boris Shingarov wrote:
On Wed, 13 Jan 2010 19:37:14 1100, Joe Neeman wrote:
>
> > It's nice to see someone else touching the page-breaking code
>
> The more I dig into it, the more questions I have.
> Back i
On Wed, 13 Jan 2010 19:37:14 1100, Joe Neeman wrote:
> It's nice to see someone else touching the page-breaking code
The more I dig into it, the more questions I have.
Back in January, we talked about vertical space estimation in the case of Prob
(i.e. markup); now I am investigating vert
Updates:
Labels: Regression
Comment #1 on issue 1042 by pnorcks: Broken regtest:
spanner-break-overshoot.ly
http://code.google.com/p/lilypond/issues/detail?id=1042
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1042 by pnorcks: Broken regtest: spanner-break-overshoot.ly
http://code.google.com/p/lilypond/issues/detail?id=1042
spanner-break-overshoot.ly broke between 2.13.15 and 2.13.16.
The attached images show the test-output
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical
New issue 1041 by brownian.box: Output suffix/prefix for score should be
documented
http://code.google.com/p/lilypond/issues/detail?id=1041
Now we can specify output filename, prefix and suffix for a score, see the
issu
Comment #12 on issue 836 by brownian.box: [in progress] output-suffix as a
(Score) context property
http://code.google.com/p/lilypond/issues/detail?id=836
Done, as issue 1041.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred
13 matches
Mail list logo
