This blog is updated daily.
A general description is here.
source(echo=TRUE) would skip lines consisting entirely of the letter t. (PR#10923)
summary.mlm() incorrectly used accessor functions to fake an "lm" object. (PR#9191)
prettyNum() was not preserving attributes, despite being explicitly documented to. (PR#8695)
It was previously undocumented what happened if a graphical parameter was passed in both '...' and 'pars' to boxplot() and bxp(), and they behaved differently. Now those passed in '...' have precedence in both cases.
Only genuinely empty statements act as 'return' in the browser, not say those starting with a comment char. (PR#9063)
o summary.mlm() incorrectly used accessor functions to fake an "lm" object. (PR#9191)
o prettyNum() was not preserving attributes, despite being explicitly documented to. (PR#8695)
o It was previously undocumented what happened if a graphical parameter was passed in both '...' and 'pars' to boxplot() and bxp(), and they behaved differently. Now those passed in '...' have precedence in both cases.
There is support for MBCS charsets in the pictex() graphics device, and rotated (by 90 degrees) text may work better.
The \u (and \U except on Windows) notation for characters which is supported by the parser in all MBCS charsets is now always interpreted as a Unicode point, even on platforms which do not encode wchar_t in Unicode. These are now a syntax error in single-byte locales.
Wide-character width functions wc[s]width are provided that overcome problems found with OS-supplied ones (and those previously used by R on Windows). This means that double-width CJK characters are now supported on all platforms. It seems that the width of some characters (and not just CJK characters) depends on which CJK locale's fonts are in use and also on the OS.
Revised wide-character classification functions are provided for use on Windows, AIX and MacOS X to replace deficient OS-supplied ones.
o There is support for MBCS charsets in the pictex() graphics device, and rotated (by 90 degrees) text may work better.
o The \u (and \U except on Windows) notation for characters which is supported by the parser in all MBCS charsets is now always interpreted as a Unicode point, even on platforms which do not encode wchar_t in Unicode. These are now a syntax error in single-byte locales.