Re: feedback to the latex-program option of lilypond-book

[John Mandereau]

[moved from lilypond-devel to bug-lilypond]
On 2008/04/26, Till Rettig wrote:
> I needed immediately to try the new command line option with xelatex, 
> and there are some smaller issues that might be interesting: for some 
> reason xelatex when called by lilypond-book dosn't find the font index, 
> so it has to build it every time anew itself, or just looks for the 
> fonts -- but as a result the compilation takes really a long time. And 
> then I was somehow astonished about the unforgivingness of
> lilypond-book: even if there is only a warning issued by xelatex I get a 
> "failed" and the compilation is stopped. The warning is issued by the 
> fontspec package that the font doesn't support a specific font feature I 
> called.

Does this warning also happen with a full document with the same
specific font feature is directly processed with xelatex?

If xelatex exits with non-zero, it should mean that the warning is to be
considered as an error.  Do you know where xelatex exit codes are
documented?


> And the last: xelatex gives this message:
> 
> Running xelatex...xelatex: /usr/local/lilypond/usr/lib/libpng12.so.0: no 
> version information available (required by xelatex)
> 
> It doesn't harm me so far, but if libpng could give its version 
> number... :-)

This warning probably happens because lilypond-book GUB wrapper changes
LD_LIBRARY_PATH.


> But it works, this is really great. Thank you. You might consider 
> closing issue 543.

I prefer to sort out problems with running xelatex first, especially the
fact that xelatex doesn't find the font index.  Could you send me a real
but not too big lilypond/xelatex sample privately?

Cheers,
John