Cairo: R graphics device using cairo graphics library for creating high-quality bitmap (PNG, JPEG, TIFF), vector (PDF, SVG, PostScript) and display (X11 and Win32) output

Cairo graphics device that can be use to create high-quality vector (PDF, PostScript and SVG) and bitmap output (PNG,JPEG,TIFF), and high-quality rendering in displays (X11 and Win32). Since it uses the same back-end for all output, copying across formats is WYSIWYG. Files are created without the dependence on X11 or other external programs. This device supports alpha channel (semi-transparent drawing) and resulting images can contain transparent and semi-transparent regions. It is ideal for use in server environments (file output) and as a replacement for other devices that don't have Cairo's capabilities such as alpha support or anti-aliasing. Backends are modular such that any subset of backends is supported.

Install the latest version of this package by entering the following in R:
install.packages("Cairo")
AuthorSimon Urbanek <Simon.Urbanek@r-project.org>, Jeffrey Horner <jeff.horner@vanderbilt.edu>
Date of publication2015-09-26 09:05:40
MaintainerSimon Urbanek <Simon.Urbanek@r-project.org>
LicenseGPL-2
Version1.5-9
http://www.rforge.net/Cairo/

View on CRAN

Files

configure.ac
src
src/xlib-backend.c
src/img-jpeg.c
src/cairotalk.c
src/img-backend.c
src/cairobem.c
src/svg-backend.h
src/cairogd.h
src/w32-backend.c
src/cairogd.c
src/svg-backend.c
src/img-tiff.h
src/cairobem.h
src/ps-backend.h
src/cconfig.h.in
src/img-tiff.c
src/ps-backend.c
src/w32-backend.h
src/Makevars.in
src/img-jpeg.h
src/pdf-backend.h
src/Makevars.win
src/pdf-backend.c
src/cairotalk.h
src/img-backend.h
src/xlib-backend.h
src/backend.h
NAMESPACE
NEWS
R
R/Cairo.R R/imgtools.R R/zzz.R
MD5
DESCRIPTION
configure
man
man/CairoFontMatch.Rd man/CairoFonts.Rd man/Cairo.onSave.Rd man/Cairo.capabilities.Rd man/Cairo.Rd man/Cairo.capture.Rd man/Cairo.serial.Rd
configure.win

Questions? Problems? Suggestions? or email at ian@mutexlabs.com.

Please suggest features or report bugs with the GitHub issue tracker.

All documentation is copyright its authors; we didn't write any of that.