[cairo] [PATCH] PS/PDF improve efficiency of text output

[Adrian Johnson]

Bryce Harrington wrote:
> I don't quite understand why the pdf backend is not being tested.
> According to autogen.sh, it's including it:
> 
> cairo will be compiled with the following surface backends:
>   image:         yes (always builtin)
>   Xlib:          yes
>   Xlib Xrender:  yes
>   Quartz:        no (disabled, use --enable-quartz to enable)
>   Native Quartz: no (disabled, use --enable-nquartz to enable)
>   XCB:           no (disabled, use --enable-xcb to enable)
>   Win32:         no (requires a Win32 platform)
>   OS2:           no (disabled, use --enable-os2 to enable)
>   PostScript:    yes
>   PDF:           yes
>   SVG:           yes
>   glitz:         no (disabled, use --enable-glitz to enable)
>   BeOS:          no (disabled, use --enable-beos to enable)
>   DirectFB:      no (disabled, use --enable-directfb to enable)
> 
> the following font backends:
>   FreeType:      yes
>   Win32:         no (requires a Win32 platform)
>   ATSUI:         no (disabled, use --enable-atsui to enable)
> 
> the following features:
>   PNG functions: yes
> 
> and the following debug options:
>   gcov support:  no
>   test surfaces: no
> 
> Any thoughts on what I might have misconfigured?

>From the autogen.sh output:

  checking for cairo's PDF backend...
  checking whether cairo's PDF backend could be enabled... yes
  configure: creating src/cairo-pdf.pc
  checking for POPPLER... configure: WARNING: PDF backend will not be
     tested since poppler >= 0.4.1 is not available
  checking for cairo's SVG backend...

Looks like poppler could not be found.

>> Is there a way I can test patches on crucible?
> 
> Yes there is.  If you have a web or ftp site where you post your
> patches, I can set up an hourly job to snag any new ones and test them.
> They'll show up on the crucible cairo report page with the others.  Just
> give me a URL and example of the filenames you use ("*.diff", "*.patch",
> "*.diff.bz2", etc.)
>
> Each patch is tested individually, so if you want to have several
> patches tested together, just create a combined patchset file.

I've put a combined patchset containing a number of small changes at:

  http://redneon.com/cairo_test

using the filename "*.diff"