Re: Issue 1294 in lilypond: Version 2.13.35 does not properly represent lyric tie

[lilypond]

Comment #10 on issue 1294 by pnorcks: Version 2.13.35 does not properly  
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294

Okay, I've just compiled the docs, locally, and I can reproduce the issue.

For lyric-tie.ly, here is what the log says for the PNG conversion:

Converting to PNG...[././0e/lily-ff07e848.eps]
GPL Ghostscript 8.71 (2010-02-10)
Copyright (C) 2010 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Substituting .notdef for uni203F in the font Sazanami-Mincho-Regular
Substituting .notdef for uni203F in the font Sazanami-Mincho-Regular


It seems that Ghostscript is having trouble loading this font.

...

This is how to reproduce without compiling the docs:

  $ lilypond -dbackend=eps -dgs-load-fonts lyric-tie.ly
  $ gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 \
       -dNOPAUSE -sDEVICE=png16m -sOutputFile="lyric-tie.png" \
       -r101 "lyric-tie.eps" -c quit

Without the "-dgs-load-fonts" flag, no "Substituting .notdef" message will  
appear, and the PNG looks fine.