Google Code changes

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

fixing PNG images

I've just been bitten by the following libpng `feature':

  IDAT: invalid distance too far back

(file `lily-ledger.png', while being processed by pdftex).
Apparently, libpng 1.6.x no longer accepts PNG images with this
problem out of the box.

Note that libpng comes with a tool called `png-fix-too-far-back' to
fix such errors in PNG files.  Is it OK to update all PNG files in the
lilypond repository?  I've been able to successfully continue
compilation with the current SVN TeXlive binaries after running this
program on all PNG images.

    Werner

ugly: accidental reminders and ties

[release/2.17.18-1-25-gb2863ab]

This code

  \relative c' {
    <f! fis'>1 ~ | q |
    <f fis'>1 ~ | q |
  }

produces the attached image.  Is this a known issue?

    Werner

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: Countdown for May 25 - 06:00GMT

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCH MERGING - notification of 'downtime'

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

mpost assertion failure

[This is the i386-linux 2013 binary of mpost, version 1.802,
 TeXLive SVN rev. 30584]

I've just got this while processing lilypond's fonts:

  mpost: ../../../texk/web2c/mplibdir/mp.w:2968:
    mp_free_value_node: Assertion `p->has_number==2' failed.

Attached are the input files to reproduce the assertion.  Note that
the code has always worked without any problems.

    Werner

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Give additional info about Xpdf versions crashing under Ubuntu (issue 9437043)

LGTM.  It's unfortunate that we need to add warnings for bugs like this
that Ubuntu has known about for years (and has already fixed once before
they broke it again!), but I think this case warrants it.

https://codereview.appspot.com/9437043/

Help with page breaking code

Hi,
the following code produces 9 pages in current master:

#(set! empty-stencil (ly:make-stencil '() empty-interval empty-interval))
\markup \fill-line { }
\markup { }
\markup { }
\markup { }
\markup { }
\markup { }
\markup { }
\markup { }
\markup { }

Basically, the first \markup produces an empty stencil with extents
(+inf.0 . -inf.0) and the page breaking code goes bonkers on that.
Since the current spacing code in issue 3330 requires this
representation for empty stencil extents, I can't really commit in this
state.

As a corollary: if extent (+inf.0 . -inf.0) throws the page breaking
code completely off-track in this case, it is unlikely that the
_current_ extent (+1.0 . -1.0) for empty stencils produces a _correct_
result either.  It will just be less noticeably wrong.

Anybody have an idea where or how to look?

--

-- 
David Kastrup

PATCHES: Countdown - May 22 - 06:00 GMT

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Uses only unpure-pure containers to articulate unpure-pure relationships. (issue 7377046)

https://codereview.appspot.com/7377046/diff/26003/lily/axis-group-interface.cc
File lily/axis-group-interface.cc (right):

https://codereview.appspot.com/7377046/diff/26003/lily/axis-group-interface.cc#newcode494
lily/axis-group-interface.cc:494:
Axis_group_interface::internal_calc_pure_relevant_grobs (Grob *me,
string grob_set_name)
Sometimes VerticalAxisGroup gets an element that is parented to another
VAG, like in issue 3359.  Now it seems these are include in
pure-relevant-grobs, and that sets the pure-Y-common of the VAG to be
the overall VerticalAlignment.  Initial staff-spacing does an infinite
recursion, because the pure-height of a VAG tries to answer in terms of
its placement in the VerticalAlignment.

https://codereview.appspot.com/7377046/

Fwd: OpenType support in Windows

I am offering a bounty of $100 for issue 1388, in particularly for an
interface that allows one to access stylistic sets in OpenType fonts.

http://code.google.com/p/lilypond/issues/detail?id=1388

Aleks