Release 1.2.0 (2006-06-27 Carl Worth <cworth@cworth.org>)=========================================================This is the culmination of the work that has gone on within the 1.1branch of cairo.There has been one API addition since the cairo 1.1.10 snapshot:	cairo_xlib_surface_get_width	cairo_xlib_surface_get_heightThere's also a new feature without any API change:	Dots can now be drawn by using CAIRO_LINE_CAP_ROUND with	degenerate sub-paths, (cairo_move_to() followed by either	cairo_close_path() or a cairo_line_to() to the same location).And at least the following bugs have been fixed: 6759  fontconfig option AntiAlias doesn't work in cairo 1.1.2 6955  Some characters aren't displayed when using xlib (cache u... 7268  positive device_offset values don't work as source * PDF emit_glyph function needs to support bitmapped glyphs * PS emit_glyph function needs to support bitmapped glyphs * SVG emit_glyph function needs to support bitmapped glyphs * PDF: minefield page one is falling back unnecessarily * PS/PDF: Fix broken placement for vertical glyphs * PS: Fix to not draw BUTT-capped zero-length dash segments * Do device offset before float->fixed conversion   http://bugzilla.gnome.org/show_bug.cgi?id=332266 * PS: Fix source surfaces with transformations * PS: Fix to not draw BUTT-capped degnerate sub-paths * PS: Don't walk off end of array when printing "~>" * Fix some memory leaks in the test suite rig * SVG: Fix memory leak when using cairo_mask * Fix EXTEND_REFLECT and EXTEND_PAD to not crash (though these are   still not yet fully implemented for surface patterns).This has been a tremendous effort by everyone, and I'm proud to havebeen a part of it. Congratulations to all contributors to cairo!Snapshot 1.1.10 (2006-06-16 Carl Worth <cworth@cworth.org>)===========================================================This is the fifth in a series of snapshots working toward the 1.2release of cairo.The primary motivation for this snapshot is to fix a long-standing bugthat had long been silent, but as of the 1.1.8 snapshot startedcausing crashes when run against 16-bit depth X servers, (often Xvncor Xnest). The fix for this adds a new CAIRO_FORMAT_RGB16_565 to theAPI.This snapshot also includes a rewrite of cairo's SVG backend toeliminate the dependency on libxml2. With this in place, cairo 1.2will not depend on any libraries that cairo 1.0 did not.As usual, there are also a few fixes for minor bugs.Snapshot 1.1.8 (2006-06-14 Carl Worth <cworth@cworth.org>)==========================================================This is the fourth in a series of snapshots working toward the 1.2release of cairo. At this point, all major features of the 1.2 releaseare in place, leaving just a few bug fixes left.In particular, there well be no additional API changes between this1.1.8 snapshot and the 1.2 release.The announcement for 1.1.6 mentioned several API changes beingconsidered. Only one of these changes was actually implemented(set_dpi -> fallback_resolution). This change does introduce onesource-level incompatibility with respect to previous 1.1.x snapshots,so see below for details.Here is an abbreviated summary of changes since the 1.1.6 snapshot:** API Change **----------------According to the plan mentioned in the 1.1.6 notes, one source-levelincompatible change has been implemented. The following threefunctions have been removed from cairo's API:	cairo_pdf_surface_set_dpi	cairo_ps_surface_set_dpi	cairo_svg_surface_set_dpiand in their place the following function has been added:	cairo_surface_set_fallback_resolutionThe signature and semantics of the function remains the same, so it isa simple matter of changing the name of the function when callingit. As a transition mechanism, this snapshot will (on many systems)build to include the old symbols so that code previously compiled willstill run. However, all source code using the old names must beupdated before it will compile. And the upcoming 1.2 release is notanticipated to include the old symbols.Finally, it should be pointed out that the old symbols never existedin the supported API of any stable release of cairo. (In the stable1.0 releases the PDF, PS, and SVG backends were advertised asexperimental and unstable.)And, as always, cairo continues to maintain source and binarycompatibility between major releases. So applications compiled againstsupported backends in a stable release of cairo (1.0.4 say) willcontinue to compile and run without modification against new majorreleases (1.2.0 say) without modification.API additions-------------The following new functions have been added to cairo's API:	cairo_surface_get_content	cairo_debug_reset_static_data	cairo_image_surface_get_data	cairo_image_surface_get_format	cairo_image_surface_get_stride	cairo_win32_font_face_create_for_hfontNew, backend-specific pkg-config files--------------------------------------In addition to the original cairo.pc file, cairo will also now installa pkg-config files for each configured backend, (for examplecairo-pdf.pc, cairo-svg.pc, cairo-xlib.pc, cairo-win32.pc, etc.) thisalso includes optional font backends (such as cairo-ft.pc) and theoptional png functionality (cairo-png.pc).These new pkg-config files should be very convenient for allowingcairo-using code to easily check for the existing of optionalfunctionality in cairo without having to write complex rules to grubthrough cairo header files or the compiled library looking forsymbols.Printing backend (PS, PDF, and SVG)-----------------------------------Improving the quality of the "printing" backends has been a priorityof the development between cairo 1.1.6 and cairo 1.1.8.The big improvement here is in the area of text output. Previously, atbest, text was output as paths without taking advantage of any fontsupport available in the output file format.Now, at the minimum text paths will be shared by using type3 fonts(for PS and PDF---and similarly, defs for SVG). Also, if possible,type3 and truetype fonts will be embedded in PostScript and PDFoutput. There are still some known bugs with this, (for example,selecting text in a cairo-generated PDF file with an embedded truetypefont does not work). So there will be some more changes in this areabefore cairo 1.2, but do try test this feature out as it exists sofar.Many thanks to Kristian H?gsberg for the truetype and type1 fontembedding.win32 backend-------------Performance improvements by preferring GDI over pixman rendering when possible.Fixes for text rendering.xlib backend------------Fix potentially big performance bug by making xlib's create_similartry harder to create a pixmap of a depth matching that of the screen.Bug fixes---------Among various other fixes, the following bugs listed in bugzilla havebeen fixed:    Bug 2488: Patch to fix pixman samping location bug (#2488).    https://bugs.freedesktop.org/show_bug.cgi?id=2488    Bug 4196: undef MIN an MAX before defining to avoid duplicate definition    https://bugs.freedesktop.org/show_bug.cgi?id=4196    Bug 4723: configure.in: Fix m4 quoting when examining pkg-config version    https://bugs.freedesktop.org/show_bug.cgi?id=4723    Bug 4882: Flag Sun's X server has having buggy_repeat.    https://bugs.freedesktop.org/show_bug.cgi?id=4882    Bug 5306: test/pdf2png: Add missing include of stdio.h    https://bugs.freedesktop.org/show_bug.cgi?id=5306    Bug 7075: Fix make clean to remove cairo.def    https://bugs.freedesktop.org/show_bug.cgi?id=7075(Many thanks to Behdad Esfahbod for helping us track down and fix manyof these.)Snapshot 1.1.6 (2006-05-04 Carl Worth <cworth@cworth.org>)==========================================================This is the third in a series of snapshots working toward the imminent1.2 release of cairo. For a list of items still needing work on thecairo 1.2 roadmap, please see:	http://cairographics.org/ROADMAPAs can be seen in that list, there are no longer any API additionsleft on the roadmap. Instead, there is a feature (PDF type 3 fonts) aperformance optimization (X server gradients) and a list of bugfixes. This gives us a fair amount of freedom to cut the 1.2 releaseat almost any point by deciding to defer remaining bug fixes tosubsequent maintenance releases such as 1.2.2 and 1.2.4.Before we will do that, we must first be wiling to commit to all thenew API additions. As a heads-up, there are a couple of potential APIchanges being considered. (Note that these are changes to new APIintroduced during 1.1 so these will not introduce APIincompatibilities compared to the stable 1.0 series). The changesbeing considered are:  cairo_get_group_target: may acquire x and y offset return	parameters. May also be eliminated in favor of	cairo_get_target assuming its role  cairo_pdf_surface_set_dpi:  cairo_ps_surface_set_dpi:  cairo_svg_surface_set_dpi: These functions may be removed in favor	of a new cairo_surface_set_fallback_resolutionAdditionally there is the possibility of a slight change in thesemantics of cairo_set_line_width. We believe the current behavior of the sequence:	cairo_set_line_width; ... change CTM ...; cairo_stroke;is buggy. It is currently behaving the same as:	... change CTM ...; cairo_set_line_width; cairo_stroke;We are considering fixing this bug before 1.2 with the hope thatnobody is already relying on the buggy behavior described here. Doshout if you suspect you might be in that position.The items included in this snapshot (since the 1.1.4 snapshot) aredescribed below.API additions-------------The long-awaited group-rendering support is now available with thefollowing function calls:	cairo_push_group	cairo_push_group_with_content	cairo_pop_group	cairo_pop_group_to_source	cairo_get_group_targetThis API provides a much more convenient mechanism for doing renderingto an intermediate surface without the need to manually create atemporary cairo_surface_t and a temporary cairo_t and clean them upafterwards.Add the following missing get function to complementcairo_surface_set_device_offset:	cairo_surface_get_device_offsetPDF backend (API addition)--------------------------The PDF backend now provides for per-page size changes, (similar towhat the PostScript backend got in the 1.1.4 snapshot). The new APIis:	cairo_pdf_surface_set_sizeXlib backend (API additions)----------------------------The following functions have been added to allow the extraction ofXlib surface:	cairo_xlib_surface_get_display	cairo_xlib_surface_get_drawable	cairo_xlib_surface_get_screen	cairo_xlib_surface_get_visual	cairo_xlib_surface_get_depthXCB backend (experimental)--------------------------Update backend so that it now compiles with the recent XCB 0.9 release.Bug fixes and memory leak cleanup---------------------------------Various little things, nothing too significant though.Snapshot 1.1.4 (2006-05-03 Carl Worth <cworth@cworth.org>)==========================================================This is the second in a series of snapshots working toward theupcoming 1.2 release of cairo. For a list of items still needing workon the cairo 1.2 roadmap, please see:	http://cairographics.org/ROADMAPThe items included in this snapshot (since the 1.1.2 snapshot) aredescribed below.PostScript backend: new printing-oriented API---------------------------------------------We anticipate that with cairo 1.2, toolkits will begin to use cairofor printing on systems that use PostScript as the spool format. Tosupport this use case, we have added 4 new function calls that arespecific to the PostScript backend:	cairo_ps_surface_set_size        cairo_ps_surface_dsc_comment        cairo_ps_surface_dsc_begin_setup        cairo_ps_surface_dsc_begin_page_setupThese functions allow variation of the page size/orientation from onepage to the next in the PostScript output. They also allow the toolkitto provide per-document and per-page printer control options in adevice-independent way, (for example, by using PPD options andemitting them as DSC comments into the PostScript output). This shouldallow toolkits to provide very fine-grained control of many optionsavailable in printers, (media size, media type, tray selection, etc.).SVG backend: builds by default, version control-----------------------------------------------The SVG backend continues to see major improvements. It is expectedthat the SVG backend will be a supported backend in the 1.2release. This backend will now be built by default if its dependencies(freetype and libxml2) are met.Additionally, the SVG backend now has flexibility with regard to whatversion of SVG it targets. It will target SVG 1.1 by default, whichwill require image fallbacks for some of the "fancier" cairocompositing operators. Or with the following new function calls:	cairo_svg_surface_restrict_to_version	cairo_svg_get_versions	cairo_svg_version_to_stringit can be made to target SVG 1.2 in which there is native support forthese compositing operators.Bug fixes---------At least the following bugs have been fixed since the 1.1.2 snapshot:crash at XRenderAddGlyphshttps://bugs.freedesktop.org/show_bug.cgi?id=4705Can't build cairo-1.1.2 on opensolaris due to " void function cannot return value"https://bugs.freedesktop.org/show_bug.cgi?id=6792Missing out-of-memory check at gfx/cairo/cairo/src/cairo-atsui-font.c:185https://bugzilla.mozilla.org/show_bug.cgi?id=336129A couple of memory leaks.Snapshot 1.1.2 (2006-04-25 Carl Worth <cworth@cworth.org>)==========================================================This is the first in a series of snapshots working toward the upcoming1.2 release of cairo. (Subsequent snapshot will use successive evennumbers for the third digit, 1.1.4, 1.1.6, etc.) This snapshot isbackwards-compatible with the 1.0 series---it makes a few APIadditions but does not remove any API.PostScript and PDF backends are no longer "experimental"--------------------------------------------------------The major theme of the 1.2 release is improved PostScript and PDFbackends for cairo. Unlike the 1.0 series, in the 1.2 series thesebackends will not be marked as experimental and will be enabled bydefault. We encourage people to test this snapshot and the PS/PDFbackends in particular as much as possible.The PostScript and PDF output is not yet ideal. * One major problem with the PostScript output is that image   fallbacks are used more often than strictly necessary, and the   image fallbacks are at a lower resolution than desired, (the   cairo_ps_surface_set_dpi call is ignored).  * The major drawback of the current PDF backend implementation is