test 2.13.7: updated freetype, fontconfig, and pango

[Graham Percival-3]

I've updated freetype, fontconfig, and pango.  I believe the result
works on OSX 10.6, but might issue a (harmless?) complaint on OSX.
The regtests look ok.  Due to the new versions for all those
font-related dependencies, I have no idea if it'll look good on any OS
(other than linux-x86, which at least could generate all the
regtests).

    http://lilypond.org/~graham/

If this looks ok, I'll give fontforge another shot, including adding
--enable-double.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[James Bailey-4]

On 02.11.2009, at 17:14, Graham Percival wrote:

I've updated freetype, fontconfig, and pango.  I believe the result

works on OSX 10.6, but might issue a (harmless?) complaint on OSX.

The regtests look ok.  Due to the new versions for all those

font-related dependencies, I have no idea if it'll look good on any OS

(other than linux-x86, which at least could generate all the

regtests).

    http://lilypond.org/~graham/

If this looks ok, I'll give fontforge another shot, including adding

--enable-double.

Cheers,

- Graham

I don't know if this even belongs here, but while checking convert-ly, I noticed something odd:

%take your pick, the output differs between versions

%\version "2.12.2"

%\version "2.13.7"

\layout {

\context {

\Score

\override RehearsalMark #'direction = #-1

\override RehearsalMark #'break-visibility = #begin-of-line-invisible

\override RehearsalMark #'self-alignment-X = #RIGHT

}

}

\score {

\new PianoStaff<<

\new Staff = RH \relative c''{ a1 \bar "|." }

\new Staff = LH \relative c{ \clef bass a1 \mark \markup \small "[35 sec.]" \bar "|." }

>>

\layout { }

}

In 2.13.7, the mark is printed under the first staff. It would appear that it now is relative to the Staff, even though RehearsalMark lives in the Score context. So, would I have to move the RehearsalMark to the Staff context in order to get it to print under the bottom-most staff?

James E. Bailey

_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Patrick McCarty-3]

On Mon, Nov 2, 2009 at 9:58 AM, James E. Bailey
<derhindemith@...> wrote:
>
> I don't know if this even belongs here, but while checking convert-ly, I
> noticed something odd:
> %take your pick, the output differs between versions
> %\version "2.12.2"
> %\version "2.13.7"

Are you referring to a difference in output between 2.12.2 and 2.13.7?
 Does the difference also appear in 2.13.6?

-Patrick


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Patrick McCarty-3]

On Mon, Nov 2, 2009 at 8:14 AM, Graham Percival
<graham@...> wrote:
> I've updated freetype, fontconfig, and pango.  I believe the result
> works on OSX 10.6, but might issue a (harmless?) complaint on OSX.
> The regtests look ok.  Due to the new versions for all those
> font-related dependencies, I have no idea if it'll look good on any OS
> (other than linux-x86, which at least could generate all the
> regtests).
>
>    http://lilypond.org/~graham/

Good news... The darwin-x86 installer runs fine on Snow Leopard and
Leopard without any Pango error messages.  The output looks fine too.

The bad news... LilyPad is missing again from the mingw installer, but
LilyPond otherwise runs fine AFAICS.

> If this looks ok, I'll give fontforge another shot, including adding
> --enable-double.

Sure!  Thanks a lot for doing this.

-Patrick


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Graham Percival-3]

On Mon, Nov 02, 2009 at 11:41:59AM -0800, Patrick McCarty wrote:
> The bad news... LilyPad is missing again from the mingw installer, but
> LilyPond otherwise runs fine AFAICS.

Growl, I forgot to manually check if it got copied and re-run it
again if not.  I should make that a script.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Graham Percival-3]

On Mon, Nov 02, 2009 at 06:58:32PM +0100, James E. Bailey wrote:

>    On 02.11.2009, at 17:14, Graham Percival wrote:
>
>      I've updated freetype, fontconfig, and pango.  I believe the result
>      works on OSX 10.6, but might issue a (harmless?) complaint on OSX.
>
>    I don't know if this even belongs here, but while checking convert-ly, I
>    noticed something odd:
>    %take your pick, the output differs between versions
>    %\version "2.12.2"
>    %\version "2.13.7"

Sorry, but I'm only working on GUB, so this isn't the place for
other problems.  If you can make a minimal example and investigate
on versions between 2.12.2 and 2.13.7 (i.e. start with 2.13.3,
then either go higher or lower depending on whether it works on
that), it might help debug it.

Oh wait; first you should check if there's already a report in the
tracker.  If not, then do the above, and add it as a
type-regression defect.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Neil Puttock]

2009/11/2 Graham Percival <graham@...>:

> Sorry, but I'm only working on GUB, so this isn't the place for
> other problems.  If you can make a minimal example and investigate
> on versions between 2.12.2 and 2.13.7 (i.e. start with 2.13.3,
> then either go higher or lower depending on whether it works on
> that), it might help debug it.

No need, it's the same bug Nicolas reported here, introduced in 2.13.4:

http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00026.html

For the time being, a workaround is to override 'after-line-breaking:

\override RehearsalMark #'after-line-breaking = ##t

Regards,
Neil


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[James Bailey-4]

On 02.11.2009, at 21:30, Neil Puttock wrote:

2009/11/2 Graham Percival <graham@...>:

Sorry, but I'm only working on GUB, so this isn't the place for

other problems.  If you can make a minimal example and investigate

on versions between 2.12.2 and 2.13.7 (i.e. start with 2.13.3,

then either go higher or lower depending on whether it works on

that), it might help debug it.

No need, it's the same bug Nicolas reported here, introduced in 2.13.4:

http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00026.html

For the time being, a workaround is to override 'after-line-breaking:

\override RehearsalMark #'after-line-breaking = ##t

Regards,

Neil

Two things before I add this to the tracker:

1) Rehearsal Marks should be placed below the system, not the first staff: http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00026.html

2)"[The] grobs are not accounted for in the vertical layout, thus leading to collisions, etc." And "there's a problem with disabling the after-line-breaking callback, especially in the case of tall Score objects."

Are these two separate issues to add to the tracker, or one issue?

James E. Bailey

_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

[Neil Puttock]

2009/11/2 James E. Bailey <derhindemith@...>:

> Two things before I add this to the tracker:
> 1) Rehearsal Marks should be placed below the system, not the first
> staff: http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00026.html
> 2)"[The] grobs are not accounted for in the vertical layout, thus leading to
> collisions, etc." And "there's a problem with disabling the
> after-line-breaking callback, especially in the case of tall Score objects."
> Are these two separate issues to add to the tracker, or one issue?

Just one, I think.

The second issue only rears its ugly head as a consequence of the workaround.

Regards,
Neil


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel