> Moreover, Ghostscript developers seem to want that `.loadfont' is > not used. > > http://bugs.ghostscript.com/show_bug.cgi?id=696823 > http://bugs.ghostscript.com/show_bug.cgi?id=696824
This is something we can trustfully ignore, I think, given that we resolve TTCs to Type42 and OTCs to bare CFF resources by ourselves. > Unfortunately, Ghostscript (ps2pdf) discards PDF destination names. > So remote PDF links do not work fine. > > http://bugs.ghostscript.com/show_bug.cgi?id=696943 > http://bugs.ghostscript.com/show_bug.cgi?id=695760 This is much more depressing :-( Isn't it possible to modify `texinfo.tex' so that it creates `invalid' remote links that only become valid after calling `ps2pdf'? Maybe this is a naive question since I don't know PDF format details. On the other hand, I can imagine to unify all separate PDF documentation files into a single `lilypond.pdf'; we then wouldn't have problems with remote PDF links. This file would have far more than 1000 pages, but due to the improved font handling it would be actually smaller than the current `notation.pdf', I think. While working on this we could also try to convince the texinfo maintainers to implement `parts', one level higher than chapters... Werner _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
