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

[Bernard Hurley]

Hi,

I should have come back on this one. I have taken on the task of organising a 
concert for a course I'm 
attending and haven't had the time to investigate this further. If you can 
waituntill after 18th March I'll 
have something more constructive to contribute.

Bernard

On Wed, Mar 03, 2010 at 01:41:57PM +0100, 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.
> 
> Hi Patrick,
> 
> 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?
> 
> > I'm still really unsure about the source of this problem.  Some more
> > things I would try:
> >
> > 1) Run `ldd lilypond' after you've installed your self-compiled
> > 2.13.12 to check for linking errors.
> >
> > 2) Run `lilypond -dshow-available-fonts 2> fonts.log' and see if the
> > log lists the "feta-alphabet" fonts.
> >
> > 3) Try compiling/installing all of LilyPond's dependencies from
> > scratch, and then compile LilyPond.  See if you get the same results.
> >
> > Let me know how it goes.  Have you tried the GNU/Linux installers from
> > lilypond.org?  Those should work out-of-the-box.
> 
> Cheers,
> Valentin
> 
> 
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond