Re: Font woes with lilypond on Ubuntu (was Re: svg output from version 2.13.12 cannot cope with numeric time signature)

[Patrick McCarty]

On 2010-03-03, Valentin Villenave wrote:
> On Thu, Jan 28, 2010 at 1:01 AM, Patrick McCarty <address@hidden> wrote:
> > On Wed, Jan 27, 2010 at 6:44 AM, Bernard Hurley <address@hidden> wrote:
> >>  Internal Error in accidentals.flat.arrowdown: monotonic is both needed 
> >> and unneeded.
> >>  Internal Error in accidentals.flat.arrowdown: monotonic is both needed 
> >> and unneeded.
> >>  Internal Error in accidentals.flat.arrowdown: Expected needed monotonic.
> >>
> >> and:
> >>
> >>  Internal Error in accidentals.sharp.arrowup: couldn't find a needed exit 
> >> from an intersection
> >>  Internal Error:
> >>  Could not find finalm
> >>
> >> and:
> >>
> >>  Invoking "fontforge -script feta26.pe feta26.pfb"...
> >>  Copyright (c) 2000-2009 by George Williams.
> >>   Executable based on sources from 22:35 GMT 22-Jun-2009.
> >>   Library based on sources from 22:35 GMT 22-Jun-2009.
> >>  Internal Error in scripts.varcoda: couldn't find a needed exit from an 
> >> intersection
> >>  Internal Error:
> >>  Could not find finalm
> >>  Internal Error in scripts.varcoda: couldn't find a needed exit from an 
> >> intersection
> >
> > These errors appear because your Fontforge was not compiled with the
> > "--enable-double" configure flag.  They disappear when
> > "--enable-double" is used.  It might be a good idea to report this
> > upstream.
> 
> I'm browsing old reports that I have left unaddressed...
> 
> Where are we wrt this issue? Is there something I can do, try and
> reproduce the problem, open a bug report somewhere, whatever?

The quoted errors above are fixed when Fontforge is compiled with the
--enable-double configure flag.

The other problem of loading the incorrect font for numeric time
signatures is still unresolved, though I suspect a corrupt Fontconfig
or corrupt Pango installation.

I don't think it's worth opening a bug report, at least at this point,
until we have further information about the source of the problem.

Thanks,
Patrick