[Top][All Lists]

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

Re: Chordmode breaks in 2.10 and 2.11

From: Brett Duncan
Subject: Re: Chordmode breaks in 2.10 and 2.11
Date: Sat, 17 Feb 2007 12:28:00 +1100
User-agent: Thunderbird (Macintosh/20061207)

Graham Percival wrote:
I don't know exactly what the deal is, but I've heard that lilypond .ps files (perhaps only since 2.10?) use some features of postscript that only very recent ghostscript versions can handle. The ghostscript that's built into Preview is too old. That's why we distribute ghostscript as part of the OSX app.
That makes sense.

So is the problem ghostscript or the sans serif font being used? And exactly which font is it, anyway?

I don't know... sorry, I've lost track of where this bug is at. Could you send me (or re-send if you have already) a minimal example of this problem? Hopefully I can get the same bug and then add it to the tracker.
Sure - this breaks on my mac:

\version "2.11.18"

\header { title = "Broken chords" }

\score {
       \new ChordNames { \chordmode {  f1 } }
       \relative c' { c1 }

but if I add \override ChordName #'font-family = #'roman after \chordmode, it's fine.


reply via email to

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