bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: svg output from version 2.13.12 cannot cope with numeric time signat


From: Patrick McCarty
Subject: Re: svg output from version 2.13.12 cannot cope with numeric time signature
Date: Sun, 24 Jan 2010 13:26:16 -0800
User-agent: Mutt/1.5.20 (2009-06-14)

On 2010-01-24, Patrick McCarty wrote:
> On 2010-01-24, Bernard Hurley wrote:
> > Using Ubuntu Linux 9.10 and lilypond version 2.13.12, if I do:
> > 
> >         lilypond -dbackend=svg test.ly
> >         
> > where test.ly is:
> > 
> > \version "2.13.12"
> > {
> >   \time 3/4
> >   c'
> > }
> > 
> > 
> > I get the output:
> > 
> > GNU LilyPond 2.13.12
> > Processing `test.ly'
> > Parsing...
> > Interpreting music... 
> > Preprocessing graphical objects...
> > Solving 1 page-breaking chunks...[1: 1 pages]
> > Drawing systems...
> > Layout output to
> > `test.svg'.../home/consultant/lilynew/lilypond/out/share/lilypond/current/scm/lily-library.scm:709:25:
> > In procedure ly:font-name in expression (ly:font-name font):
> > /home/consultant/lilynew/lilypond/out/share/lilypond/current/scm/lily-library.scm:709:25:
> > Wrong type argument in position 1 (expecting Font_metric):
> > "CharisSIL"
> > 
> > It works as expected without the "\time 3/4"
> 
> This type of error normally shouldn't happen, because the only fonts
> that are passed to "font-name-style" are the Emmentaler and Aybabtu
> OTF fonts, and the feta-alphabet* Type1 fonts.
> 
> I can't think of a case where another font would slip through, unless
> there is a problem with one of LilyPond's dependencies.

I should be a little more explicit with my diagnosis:

In this specific example, using "\time 3/4", one of the feta-alphabet
Type 1 fonts should be loaded.

But, based on your output, the "CharisSIL" font is loaded, which is
not expected.

The numeric glyphs are loaded with Pango via Fontconfig, so maybe
there might be a problem with one of these two dependencies on your
system.

-Patrick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]