> Type 2 charstrings have some extensions like the `random' > operator which isn't supported in Type 1 fonts.
Ah. So the reason otf -> pfa usually works is because most fonts contain "regular" character outlines that are just packaged as CFF, without actually making use of the new features. (Of course the conversion loses all the OpenType tables, but this can probably be made up for by extra intelligence in the typesetting program.) > There is another Lilypond option to let the fonts be loaded by > GhostScript directly. [...] > A nice side effect is that the EPS files become much smaller, > but of course they are no longer self-contained. > Again, grops understands this just fine, but you *must* use > GhostScript afterwards to further process the output file. I _knew_ there had to be some way to tell Lilypond to behave differently. And in most cases I guess it's no big restriction, because we normally use ghostscript anyway at the end to produce a PDF to distribute. The only downside is that the PostScript file can't be sent to the printer directly. > Using -dbackend=eps, you don't need this since a bounding box > gets emitted. I noticed that for very short fragments the bounding box is wider (it includes the whole width of the line) than the actual output, which is probably useful if you import several pieces and want them all nicely aligned...
