This blog is updated daily.
A general description is here.
There is a new ‘antialias’ argument to ‘windows()’, ‘win.print()’ and the bitmap devices. This is an option that can be set in ‘windows.options()’ to set the default for ‘windows()’ (and ‘win.graph()’).
This effectively gives a hint to the Windows plotting system. Whether anti-aliasing is used principally depends on the OS settings: this argument should at least be able to turn it off. The default behaviour (unchanged from before) is that Windows will use anti-aliasing for screen devices (and bitmap devices, as they plot on a hidden screen) if ClearType has been enabled.
The argument can also be used for the cairographics-based versions of the bitmap devices.
There is support for cairographics-based devices using the same code as on Unix-alikes. This can be selected by the new ‘type’ argument of the bitmap devices ‘bmp()’, ‘jpeg()’, ‘png()’ and ‘tiff()’, and devices ‘svg()’, ‘cairo_pdf()’ and ‘cairo_ps()’ are now available on Windows.
[Experimental and not compiled in by default.
To experiment with them, follow the instructions in the ‘R Installation and Administration Manual’.]
All the Windows-specific graphics devices now have a ‘family’ argument. If non-empty this specifies an initial family to be used for fonts 1-4. If empty the fonts specified in the ‘Rdevga’ configuration file are used for the Windows GDI devices and ‘"sans"’ for cairographics-based devices.
This will generally be a Windows font name such as ‘"Lucida Bright"’ or one of the device-independent names (‘"sans"’, ‘"serif"’ and ‘"mono"’). Outside Western Europe you may need to select a family that better supports your locale such as ‘"Arial MS Unicode"’ or one specific to Chinese/Korean/Thai ....
‘Rzlib.dll’ (sometimes used in packages _via_ ‘$(ZLIB_LIBS)’) does not include the buggy gzio interface from zlib 1.2.5.