Updates:
Labels: -Type-Documentation Type-Critical
Comment #3 on issue 2733 by [email protected]: lilypond-book via dvi and ps no
longer seems to work
http://code.google.com/p/lilypond/issues/detail?id=2733
Here is some analysis: after private mail, it turns out that the version
used was 2.15.42 (alternatively 2.14.2). The reporter of the problem
confirmed that the problem occured with GhostScript 9.04 on her system, but
not with GhostScript 9.05. GhostScript 9.05 contains the full URW set of
basic PostScript fonts (so including Century Schoolbook).
However, the above error message is from trying to open a font with an
absolute font name:
/home/newlily/lilypond/usr/share/lilypond/current/fonts/otf/CenturySchL-Ital.otf
If a file tries doing that, it will not be portable (whether or not the
font is actually at the specified place, with ps2pdf maybe refusing to open
because of security considerations).
How does this absolute font name get into the PostScript file in the first
place? Either it is placed there by LilyPond, or by dvips -Ppdf. The
latter presumably _could_ validly produce unportable PostScript on the
assumption that the target is to be converted using ps2pdf anyway. But I
would be quite surprised if it did. So it would be important to figure out
just where in the processing chain the absolute paths to fonts (rather than
an actually embedded font itself) creeps into the PostScript and see what
we can do about that.
If anybody can find out more about this phenomenon: this seems like the
sort of thing we would likely want to have more clarity about before
releasing 2.16. Even if the result might just be "please use GhostScript
9.05 or later".
