Re: Chordmode breaks in 2.10 and 2.11

[Graham Percival]

Brett Duncan wrote:
> Graham Percival wrote:

> > > If I specify Postscript for the output, the resulting PS file will 
> > > not open in Preview (nor for that matter in GraphicConverter, which 
> > > reports the file as corrupt). However, the PS file *will* open in 
> > > KGhostView and KPDF (both running in XDarwin) and appear to be fine.
> >
> > This is normal.
> In what sense? I can use Preview (and GraphicConverter) to open PS files 
> that I had previously created with LP, it's only PS files I'm creating 
> now that are problematic.

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.

> > See the "notes for the OSX app" in the unstable docs; I changed them 
> > about a month ago.  Follow those new instructors, and let me know if 
> > that improves things.
>
> Went through that, but it made no difference.

Huh.  I'm afraid that I'm out of ideas, then.

> However, I had wondered if there was a font issue - it occurred to me 
> that the thing that is different about the chord names compared to other 
> text on the page is they appear in a sans serif font - so I added
>
>    \override ChordName #'font-family = #'roman
>
> to my file... and now LP typesets the file without error!
>
> 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.

Cheers,
- Graham