root@ntg.nl (Cron Daemon) writes:
------------------------------------------------------------------------ r6103 | luigi | 2016-08-23 12:39:29 +0200 (Tue, 23 Aug 2016) | 1 line Changed paths: [...] A /tags/0.98.3/source/libs/cairo A /tags/0.98.3/source/libs/cairo/ChangeLog A /tags/0.98.3/source/libs/cairo/Makefile.am A /tags/0.98.3/source/libs/cairo/Makefile.in A /tags/0.98.3/source/libs/cairo/README A /tags/0.98.3/source/libs/cairo/ac A /tags/0.98.3/source/libs/cairo/ac/cairo.ac A /tags/0.98.3/source/libs/cairo/ac/withenable.ac A /tags/0.98.3/source/libs/cairo/aclocal.m4 A /tags/0.98.3/source/libs/cairo/cairo A /tags/0.98.3/source/libs/cairo/cairo/Makefile.am A /tags/0.98.3/source/libs/cairo/cairo/Makefile.in A /tags/0.98.3/source/libs/cairo/cairo-PATCHES A /tags/0.98.3/source/libs/cairo/cairo-PATCHES/ChangeLog A /tags/0.98.3/source/libs/cairo/cairo-PATCHES/TL-Changes A /tags/0.98.3/source/libs/cairo/cairo-features.h.in A /tags/0.98.3/source/libs/cairo/cairo-src [...]
Does LuaTeX use Cairo for PDF generation in any manner? Or is that just included for separate use from Lua? The reason I ask is that Cairo does not particularly suited to generating actual PDF _Documents_ (replete with Metadata, TOC, crossreferences and other stuff) rather than just graphics to be embedded elsewhere. If you _do_ generate whole PDF _documents_ with it, the manner in which you do could be interesting for LilyPond as well which currently runs almost all of its output through Ghostscript for processing (including generating PDF and PNG) at considerable impact on performance and various problems with font inclusion/subsetting. Thanks for any insight you can provide here! -- David Kastrup