openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

File R-release.diff of Package R (Revision 0834f59f255673369742f058bf4a6bbc)

Currently displaying revision 0834f59f255673369742f058bf4a6bbc , Show latest

# cd *inside* the ...../R-4.4.1/  directory, and do
#      zcat ..../R-release.diff.gz | patch -p1 -E
# ---------                          =====
# You need a "g[un]zip capable zcat", and canNOT use Solaris "patch"!
# Rather get ("gzip" and)  "diffutils" from any GNU mirror.
#
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/SVN-REVISION R-patched/SVN-REVISION
--- R-release-orig/SVN-REVISION	2024-06-14 09:02:21.000000000 +0200
+++ R-patched/SVN-REVISION	2024-10-19 01:32:16.433816794 +0200
@@ -1,2 +1,2 @@
-Revision: 86737
-Last Changed Date: 2024-06-14
+Revision: 87246
+Last Changed Date: 2024-10-18
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/VERSION R-patched/VERSION
--- R-release-orig/VERSION	2024-06-14 09:00:02.000000000 +0200
+++ R-patched/VERSION	2024-07-16 11:38:48.028714071 +0200
@@ -1 +1 @@
-4.4.1
+4.4.1 Patched
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/FAQ R-patched/doc/FAQ
--- R-release-orig/doc/FAQ	2024-06-14 09:02:22.000000000 +0200
+++ R-patched/doc/FAQ	2024-10-19 01:32:17.541128330 +0200
@@ -85,7 +85,7 @@
   7.28 Why is read.table() so inefficient?
   7.29 What is the difference between package and library?
   7.30 I installed a package but the functions are not there
-  7.31 Why doesn’t R think these numbers are equal?
+  7.31 Why doesn't R think these numbers are equal?
   7.32 How can I capture or ignore errors in a long simulation?
   7.33 Why are powers of negative numbers wrong?
   7.34 How can I save the result of each iteration in a loop into a separate file?
@@ -121,8 +121,8 @@
 1.1 Legalese
 ============
 
-Copyright © 1998–2020 Kurt Hornik
-Copyright © 2021–2024 R Core Team
+Copyright © 1998-2020 Kurt Hornik
+Copyright © 2021-2024 R Core Team
 
    This document is free software; you can redistribute it and/or modify it
 under the terms of the GNU General Public License as published by the Free
@@ -151,7 +151,7 @@
 ========================
 
 In publications, please refer to this FAQ as Hornik and R Core Team (2024),
-“The R FAQ”, and give the above, _official_ URL:
+"The R FAQ", and give the above, _official_ URL:
 
      @Misc{,
        author        = {Kurt Hornik and the R Core Team},
@@ -172,9 +172,9 @@
 Feedback via email to <R-devel@R-project.org> is most welcome.
 
    Features specific to the Windows and macOS ports of R are described in
-the “R for Windows FAQ”
-(https://CRAN.R-project.org/bin/windows/base/rw-FAQ.html) and the “R for Mac
-OS X FAQ” (https://CRAN.R-project.org/bin/macosx/RMacOSX-FAQ.html).  If you
+the "R for Windows FAQ"
+(https://CRAN.R-project.org/bin/windows/base/rw-FAQ.html) and the "R for Mac
+OS X FAQ" (https://CRAN.R-project.org/bin/macosx/RMacOSX-FAQ.html).  If you
 have information on Mac or Windows systems that you think should be added to
 this document, please let us know.
 
@@ -190,7 +190,7 @@
 files.
 
    The design of R has been heavily influenced by two existing languages:
-Becker, Chambers & Wilks’ S (*note What is S?::) and Sussman’s Scheme
+Becker, Chambers & Wilks' S (*note What is S?::) and Sussman's Scheme
 (http://community.schemewiki.org/?scheme-faq).  Whereas the resulting
 language is very similar in appearance to S, the underlying implementation
 and semantics are derived from Scheme.  *Note What are the differences
@@ -205,8 +205,8 @@
 models, nonlinear regression models, time series analysis, classical
 parametric and nonparametric tests, clustering and smoothing.  There is also
 a large set of functions which provide a flexible graphical environment for
-creating various kinds of data presentations.  Additional modules (“add-on
-packages”) are available for a variety of specific purposes (*note R Add-On
+creating various kinds of data presentations.  Additional modules ("add-on
+packages") are available for a variety of specific purposes (*note R Add-On
 Packages::).
 
    R was initially written by Ross Ihaka <Ross.Ihaka@R-project.org> and
@@ -215,7 +215,7 @@
 addition, a large group of individuals has contributed to R by sending code
 and bug reports.
 
-   Since mid-1997 there has been a core group (the “R Core Team”) who can
+   Since mid-1997 there has been a core group (the "R Core Team") who can
 modify the R source code archive, currently consisting of
      John Chambers,
      Peter Dalgaard,
@@ -243,7 +243,7 @@
    R has a home page at <https://www.R-project.org/>.  It is free software
 (https://www.gnu.org/philosophy/free-sw.html) distributed under a GNU-style
 copyleft (https://www.gnu.org/copyleft/copyleft.html), and an official part
-of the GNU (https://www.gnu.org/) project (“GNU S”).
+of the GNU (https://www.gnu.org/) project ("GNU S").
 
 2.2 What machines does R run on?
 ================================
@@ -265,11 +265,11 @@
 2.3 What is the current version of R?
 =====================================
 
-R uses a ‘major.minor.patchlevel’ numbering scheme.  Based on this, there
-are the current release version of R (‘r-release’) as well as two
+R uses a 'major.minor.patchlevel' numbering scheme.  Based on this, there
+are the current release version of R ('r-release') as well as two
 development versions of R, a patched version of the current release
-(‘r-patched’) and one working towards the next minor or eventually major
-(‘r-devel’) releases of R, respectively.  New features are typically
+('r-patched') and one working towards the next minor or eventually major
+('r-devel') releases of R, respectively.  New features are typically
 introduced in r-devel, while r-patched is for bug fixes mostly.
 
    See <https://CRAN.R-project.org/sources.html> for the current versions of
@@ -279,13 +279,15 @@
 ==========================
 
 Sources, binaries and documentation for R can be obtained via CRAN, the
-“Comprehensive R Archive Network” (see *note What is CRAN?::).
+"Comprehensive R Archive Network" (see *note What is CRAN?::).
 
    Sources are also available via <https://svn.R-project.org/R/>, the R
 Subversion repository, but currently not via anonymous rsync (nor CVS).
 
    Tarballs with daily snapshots of the r-devel and r-patched development
-versions of R can be found at <https://stat.ethz.ch/R/daily/>.
+versions of R can be found at
+<https://cran.r-project.org/src/base-prerelease>.  An alternative source is
+<https://stat.ethz.ch/R/daily/>.
 
 2.5 How can R be installed?
 ===========================
@@ -303,7 +305,7 @@
    Otherwise, you can compile and install R yourself, which can be done very
 easily under a number of common Unix-like platforms (see *note What machines
 does R run on?::).  The file ‘INSTALL’ that comes with the R distribution
-contains a brief introduction, and the “R Installation and Administration”
+contains a brief introduction, and the "R Installation and Administration"
 guide (*note What documentation exists for R?::) has full details.
 
    Note that you need a FORTRAN 90 compiler as well as a C compiler to build
@@ -319,7 +321,7 @@
 front-end called ‘R’ are created and copied to the ‘bin’ directory.  You can
 copy the script to a place where users can invoke it, for example to
 ‘/usr/local/bin’.  In addition, HTML versions of the R manuals (e.g.,
-‘R-exts.html’, the “Writing R Extensions” manual) are built in the
+‘R-exts.html’, the "Writing R Extensions" manual) are built in the
 ‘doc/manual’ subdirectory.
 
    Use ‘make pdf’ to build PDF (Portable Document Format) versions of the R
@@ -332,7 +334,7 @@
    Finally, use ‘make check’ to find out whether your R system works
 correctly.
 
-   You can also perform a “system-wide” installation using ‘make install’.
+   You can also perform a "system-wide" installation using ‘make install’.
 By default, this will install to the following directories:
 
 ‘${prefix}/bin’
@@ -340,8 +342,8 @@
 ‘${prefix}/man/man1’
      the man page
 ‘${prefix}/lib/R’
-     all the rest (libraries, on-line help system, ...).  This is the “R
-     Home Directory” (‘R_HOME’) of the installed system.
+     all the rest (libraries, on-line help system, ...).  This is the "R
+     Home Directory" (‘R_HOME’) of the installed system.
 
 In the above, ‘prefix’ is determined during configuration (typically
 ‘/usr/local’) and can be set by running ‘configure’ with the option
@@ -368,19 +370,19 @@
    The same directory has links to snapshots of the r-patched and r-devel
 versions of R.
 
-   See the “R for Windows FAQ”
+   See the "R for Windows FAQ"
 (https://CRAN.R-project.org/bin/windows/base/rw-FAQ.html) for more details.
 
 2.5.3 How can R be installed (Mac)
 ----------------------------------
 
 The ‘bin/macosx’ directory of a CRAN site contains a standard Apple
-installer package to run on macOS 10.13 (‘High Sierra’) or later, and
-another which runs only on ‘Apple Silicon’ Macs under macOS 11 (‘Big Sur’)
+installer package to run on macOS 10.13 ('High Sierra') or later, and
+another which runs only on 'Apple Silicon' Macs under macOS 11 ('Big Sur')
 or later.  Once downloaded and executed, the installer will install the
 current release of R and R.app, the macOS GUI.  This port of R for macOS is
 maintained by Simon Urbanek <Simon.Urbanek@R-project.org> (and previously by
-Stefano Iacus).  The “R for macOS FAQ”
+Stefano Iacus).  The "R for macOS FAQ"
 (https://CRAN.R-project.org/bin/macosx/RMacOSX-FAQ.html) has more details.
 
    Snapshots of the r-patched and r-devel versions of R are available as
@@ -390,7 +392,7 @@
 =======================================
 
 Binary distributions of R are available on many Unix-like OSes: only some
-can be mentioned here so check your OS’s search facilities to see if one is
+can be mentioned here so check your OS's search facilities to see if one is
 available for yours.
 
    The ‘bin/linux’ directory of a CRAN site contains R packages for Debian
@@ -401,7 +403,7 @@
 maintenance tool.  Use e.g. ‘apt-get install r-base r-recommended’ to
 install the R environment and recommended packages.  If you also want to
 build R packages from source, also run ‘apt-get install r-base-dev’ to
-obtain the additional tools required for this.  So-called “backports” of the
+obtain the additional tools required for this.  So-called "backports" of the
 current R packages for at least the “stable” distribution of Debian are
 provided by Johannes Ranke, and available from CRAN.  See
 <https://CRAN.R-project.org/bin/linux/debian/index.html> for details on R
@@ -410,12 +412,12 @@
 Michael Rutter, see <https://CRAN.R-project.org/bin/linux/ubuntu/index.html>
 for instructions.
 
-   R binaries for Fedora, maintained by Tom “Spot” Callaway, are provided as
+   R binaries for Fedora, maintained by Tom "Spot" Callaway, are provided as
 part of the Fedora distribution and can be accessed through ‘yum’, the RPM
-installer/updater.  Note that the “Software” application (gnome-software),
+installer/updater.  Note that the "Software" application (gnome-software),
 which is the default GUI for software installation in Fedora 20, cannot be
 used to install R. It is therefore recommended to use the yum command line
-tool.  The Fedora R RPM is a “meta-package” which installs all the user and
+tool.  The Fedora R RPM is a "meta-package" which installs all the user and
 developer components of R (available separately as ‘R-core’ and ‘R-devel’),
 as well as ‘R-java’, which ensures that R is configured for use with Java.
 The R RPM also installs the standalone R math library (‘libRmath’ and
@@ -449,19 +451,19 @@
 
    The R distribution also comes with the following manuals.
 
-   • “An Introduction to R” (‘R-intro’) includes information on data types,
+   • "An Introduction to R" (‘R-intro’) includes information on data types,
      programming elements, statistical modeling and graphics.  This document
-     is based on the “Notes on S-PLUS” by Bill Venables and David Smith.
-   • “Writing R Extensions” (‘R-exts’) currently describes the process of
-     creating R add-on packages, writing R documentation, R’s system and
+     is based on the "Notes on S-PLUS" by Bill Venables and David Smith.
+   • "Writing R Extensions" (‘R-exts’) currently describes the process of
+     creating R add-on packages, writing R documentation, R's system and
      foreign language interfaces, and the R API.
-   • “R Data Import/Export” (‘R-data’) is a guide to importing and exporting
+   • "R Data Import/Export" (‘R-data’) is a guide to importing and exporting
      data to and from R.
-   • “The R Language Definition” (‘R-lang’), a first version of the
-     “Kernighan & Ritchie of R”, explains evaluation, parsing, object
+   • "The R Language Definition" (‘R-lang’), a first version of the
+     "Kernighan & Ritchie of R", explains evaluation, parsing, object
      oriented programming, computing on the language, and so forth.
-   • “R Installation and Administration” (‘R-admin’).
-   • “R Internals” (‘R-ints’) is a guide to R’s internal structures.  (Added
+   • "R Installation and Administration" (‘R-admin’).
+   • "R Internals" (‘R-ints’) is a guide to R's internal structures.  (Added
      in R 2.4.0.)
 
    An annotated bibliography (BibTeX format) of R-related publications can
@@ -471,44 +473,44 @@
 
    Books on R by R Core Team members include
 
-     John M. Chambers (2008), “Software for Data Analysis: Programming with
-     R”.  Springer, New York, ISBN 978-0-387-75935-7,
+     John M. Chambers (2008), "Software for Data Analysis: Programming with
+     R". Springer, New York, ISBN 978-0-387-75935-7,
      <https://johnmchambers.su.domains/Rbook/>.
 
-     Peter Dalgaard (2008), “Introductory Statistics with R”, 2nd edition.
+     Peter Dalgaard (2008), "Introductory Statistics with R", 2nd edition.
      Springer, ISBN 978-0-387-79053-4,
      <http://publicifsv.sund.ku.dk/~pd/ISwR.html>.
 
-     Robert Gentleman (2008), “R Programming for Bioinformatics”.  Chapman &
+     Robert Gentleman (2008), "R Programming for Bioinformatics".  Chapman &
      Hall/CRC, Boca Raton, FL, ISBN 978-1-420-06367-7,
      <https://bioconductor.org/help/publications/books/r-programming-for-bioinformatics/>.
 
-     Stefano M. Iacus (2008), “Simulation and Inference for Stochastic
-     Differential Equations: With R Examples”.  Springer, New York, ISBN
+     Stefano M. Iacus (2008), "Simulation and Inference for Stochastic
+     Differential Equations: With R Examples".  Springer, New York, ISBN
      978-0-387-75838-1.
 
-     Deepayan Sarkar (2007), “Lattice: Multivariate Data Visualization with
-     R”.  Springer, New York, ISBN 978-0-387-75968-5.
+     Deepayan Sarkar (2007), "Lattice: Multivariate Data Visualization with
+     R". Springer, New York, ISBN 978-0-387-75968-5.
 
-     W. John Braun and Duncan J. Murdoch (2007), “A First Course in
-     Statistical Programming with R”.  Cambridge University Press,
-     Cambridge, ISBN 978-0521872652.
+     W. John Braun and Duncan J. Murdoch (2007), "A First Course in
+     Statistical Programming with R". Cambridge University Press, Cambridge,
+     ISBN 978-0521872652.
 
-     P. Murrell (2005), “R Graphics”, Chapman & Hall/CRC, ISBN
+     P. Murrell (2005), "R Graphics", Chapman & Hall/CRC, ISBN
      1-584-88486-X,
      <https://www.stat.auckland.ac.nz/~paul/RGraphics/rgraphics.html>.
 
-     William N. Venables and Brian D. Ripley (2002), “Modern Applied
-     Statistics with S” (4th edition).  Springer, ISBN 0-387-95457-0,
+     William N. Venables and Brian D. Ripley (2002), "Modern Applied
+     Statistics with S" (4th edition).  Springer, ISBN 0-387-95457-0,
      <https://www.stats.ox.ac.uk/pub/MASS4/>.
 
-     Jose C. Pinheiro and Douglas M. Bates (2000), “Mixed-Effects Models in
-     S and S-Plus”.  Springer, ISBN 0-387-98957-0.
+     Jose C. Pinheiro and Douglas M. Bates (2000), "Mixed-Effects Models in
+     S and S-Plus".  Springer, ISBN 0-387-98957-0.
 
-   Last, but not least, Ross’ and Robert’s experience in designing and
-implementing R is described in Ihaka & Gentleman (1996), “R: A Language for
-Data Analysis and Graphics”, _Journal of Computational and Graphical
-Statistics_, *5*, 299–314 (doi: 10.1080/10618600.1996.10474713
+   Last, but not least, Ross' and Robert's experience in designing and
+implementing R is described in Ihaka & Gentleman (1996), "R: A Language for
+Data Analysis and Graphics", _Journal of Computational and Graphical
+Statistics_, *5*, 299-314 (doi: 10.1080/10618600.1996.10474713
 (https://doi.org/10.1080/10618600.1996.10474713)).
 
 2.8 Citing R
@@ -544,10 +546,10 @@
      A moderated list for announcements on the availability of new or
      enhanced contributed packages.
 ‘R-help’
-     The ‘main’ R mailing list, for discussion about problems and solutions
+     The 'main' R mailing list, for discussion about problems and solutions
      encountered using R, including using R packages in the standard R
-     distribution and on CRAN; announcements (not covered by ‘R-announce’ or
-     ‘R-packages’); the availability of new functionality for R and
+     distribution and on CRAN; announcements (not covered by 'R-announce' or
+     'R-packages'); the availability of new functionality for R and
      documentation of R; and for posting nice examples and benchmarks.
 ‘R-devel’
      This list is for questions and discussion about code development in R.
@@ -593,7 +595,7 @@
 2.10 What is CRAN?
 ==================
 
-The “Comprehensive R Archive Network” (CRAN) is a collection of sites which
+The "Comprehensive R Archive Network" (CRAN) is a collection of sites which
 carry identical material, consisting of the R distribution(s), the
 contributed extensions, documentation for R, and binaries.
 
@@ -613,7 +615,7 @@
 Windows).  CRAN also provides access to documentation on R, existing mailing
 lists and the R Bug Tracking system.
 
-   Since March 2016, “old” material is made available from a central CRAN
+   Since March 2016, "old" material is made available from a central CRAN
 archive server (<https://CRAN-archive.R-project.org/>).
 
    Please always use the URL of the master site when referring to CRAN.
@@ -630,7 +632,7 @@
 purposes (e.g., in business or in consulting).  The GPL, like all Open
 Source licenses, permits all and any use of the package.  It only restricts
 distribution of R or of other programs containing code from R. This is made
-clear in clause 6 (“No Discrimination Against Fields of Endeavor”) of the
+clear in clause 6 ("No Discrimination Against Fields of Endeavor") of the
 Open Source Definition (https://opensource.org/osd):
 
      The license must not restrict anyone from making use of the program in
@@ -647,7 +649,7 @@
 
    Most add-on packages, including all recommended ones, also explicitly
 allow commercial use in this way.  A few packages are restricted to
-“non-commercial use”; you should contact the author to clarify whether these
+"non-commercial use"; you should contact the author to clarify whether these
 may be used or seek the advice of your legal counsel.
 
    None of the discussion in this section constitutes legal advice.  The R
@@ -658,7 +660,7 @@
 
 The name is partly based on the (first) names of the first two R authors
 (Robert Gentleman and Ross Ihaka), and partly a play on the name of the Bell
-Labs language ‘S’ (*note What is S?::).
+Labs language 'S' (*note What is S?::).
 
 2.13 What is the R Foundation?
 ==============================
@@ -681,8 +683,8 @@
 to the best in SVN, daily built and checked packages, mailing lists, bug
 tracking, message boards/forums, site hosting, permanent file archival, full
 backups, and total web-based administration.  For more information, see the
-R-Forge web page and Stefan Theußl and Achim Zeileis (2009), “Collaborative
-software development using R-Forge”, _The R Journal_, *1*(1):9–14.
+R-Forge web page and Stefan Theußl and Achim Zeileis (2009), "Collaborative
+software development using R-Forge", _The R Journal_, *1*(1):9-14.
 
 3 R and S
 *********
@@ -705,53 +707,53 @@
    The evolution of the S language is characterized by four books by John
 Chambers and coauthors, which are also the primary references for S.
 
-   • Richard A. Becker and John M. Chambers (1984), “S. An Interactive
-     Environment for Data Analysis and Graphics,” Monterey: Wadsworth and
+   • Richard A. Becker and John M. Chambers (1984), "S. An Interactive
+     Environment for Data Analysis and Graphics," Monterey: Wadsworth and
      Brooks/Cole.
 
-     This is also referred to as the “_Brown Book_”, and of historical
+     This is also referred to as the "_Brown Book_", and of historical
      interest only.
 
-   • Richard A. Becker, John M. Chambers and Allan R. Wilks (1988), “The New
-     S Language,” London: Chapman & Hall.
+   • Richard A. Becker, John M. Chambers and Allan R. Wilks (1988), "The New
+     S Language," London: Chapman & Hall.
 
-     This book is often called the “_Blue Book_”, and introduced what is now
+     This book is often called the "_Blue Book_", and introduced what is now
      known as S version 2.
 
-   • John M. Chambers and Trevor J. Hastie (1992), “Statistical Models in
-     S,” London: Chapman & Hall.
+   • John M. Chambers and Trevor J. Hastie (1992), "Statistical Models in
+     S," London: Chapman & Hall.
 
-     This is also called the “_White Book_”, and introduced S version 3,
+     This is also called the "_White Book_", and introduced S version 3,
      which added structures to facilitate statistical modeling in S.
 
-   • John M. Chambers (1998), “Programming with Data,” New York: Springer,
+   • John M. Chambers (1998), "Programming with Data," New York: Springer,
      ISBN 0-387-98503-4 (<https://johnmchambers.su.domains/Sbook/>).
 
-     This “_Green Book_” describes version 4 of S, a major revision of S
+     This "_Green Book_" describes version 4 of S, a major revision of S
      designed by John Chambers to improve its usefulness at every stage of
      the programming process.
 
    See <https://johnmchambers.su.domains/papers/96.7.ps> for further
-information on the “Evolution of the S Language”.
+information on the "Evolution of the S Language".
 
 3.2 What is S-PLUS?
 ===================
 
 S-PLUS is a value-added version of S sold by TIBCO Software Inc
-(https://www.tibco.com/) as ‘TIBCO Spotfire S+’.  See
+(https://www.tibco.com/) as 'TIBCO Spotfire S+'.  See
 <https://en.wikipedia.org/wiki/S-PLUS> for more information.
 
 3.3 What are the differences between R and S?
 =============================================
 
 We can regard S as a language with three current implementations or
-“engines”, the “old S engine” (S version 3; S-PLUS 3.x and 4.x), the “new S
-engine” (S version 4; S-PLUS 5.x and above), and R. Given this
-understanding, asking for “the differences between R and S” really amounts
+"engines", the "old S engine" (S version 3; S-PLUS 3.x and 4.x), the "new S
+engine" (S version 4; S-PLUS 5.x and above), and R. Given this
+understanding, asking for "the differences between R and S" really amounts
 to asking for the specifics of the R implementation of the S language, i.e.,
 the difference between the R and S _engines_.
 
-   For the remainder of this section, “S” refers to the S engines and not
+   For the remainder of this section, "S" refers to the S engines and not
 the S language.
 
 3.3.1 Lexical scoping
@@ -776,7 +778,7 @@
        n * sq()
      }
 
-   Under S, ‘sq()’ does not “know” about the variable ‘n’ unless it is
+   Under S, ‘sq()’ does not "know" about the variable ‘n’ unless it is
 defined globally:
 
      S> cube(2)
@@ -786,13 +788,13 @@
      S> cube(2)
      [1] 18
 
-   In R, the “environment” created when ‘cube()’ was invoked is also looked
+   In R, the "environment" created when ‘cube()’ was invoked is also looked
 in:
 
      R> cube(2)
      [1] 8
 
-   As a more “interesting” real-world problem, suppose you want to write a
+   As a more "interesting" real-world problem, suppose you want to write a
 function which returns the density function of the r-th order statistic from
 a sample of size n from a (continuous) distribution.  For simplicity, we
 shall use both the distribution and density functions distribution as
@@ -814,7 +816,7 @@
        f
      }
 
-Rather tricky, isn’t it?  The code uses the fact that in S, functions are
+Rather tricky, isn't it?  The code uses the fact that in S, functions are
 just lists of special mode with the function body as the last argument, and
 hence does not work in R (one could make the idea work, though).
 
@@ -839,7 +841,7 @@
        }
      }
 
-This seems to be the “natural” implementation, and it works because the free
+This seems to be the "natural" implementation, and it works because the free
 variables in the returned function can be looked up in the defining
 environment (this is lexical scope).
 
@@ -847,7 +849,7 @@
 along with all variable bindings needed for evaluating it.  Since in the
 above version, the free variables in the value function are not modified,
 you can actually use it in S as well if you abstract out the closure
-operation into a function ‘MC()’ (for “make closure”):
+operation into a function ‘MC()’ (for "make closure"):
 
      dorder <- function(n, r, pfun, dfun) {
        con <- round(exp(lgamma(n + 1) - lgamma(r) - lgamma(n - r + 1)))
@@ -858,7 +860,7 @@
      }
 
    Given the appropriate definitions of the closure operator, this works in
-both R and S, and is much “cleaner” than a substitute/eval solution (or one
+both R and S, and is much "cleaner" than a substitute/eval solution (or one
 which overrules the default scoping rules by using explicit access to
 evaluation frames, as is of course possible in both R and S).
 
@@ -897,11 +899,11 @@
    Nested lexically scoped functions allow using function closures and
 maintaining local state.  A simple example (taken from Abelson and Sussman)
 is obtained by typing ‘demo("scoping")’ at the R prompt.  Further
-information is provided in the standard R reference “R: A Language for Data
-Analysis and Graphics” (*note What documentation exists for R?::) and in
-Robert Gentleman and Ross Ihaka (2000), “Lexical Scope and Statistical
-Computing”, _Journal of Computational and Graphical Statistics_, *9*,
-491–508 (doi: 10.1080/10618600.2000.10474895
+information is provided in the standard R reference "R: A Language for Data
+Analysis and Graphics" (*note What documentation exists for R?::) and in
+Robert Gentleman and Ross Ihaka (2000), "Lexical Scope and Statistical
+Computing", _Journal of Computational and Graphical Statistics_, *9*,
+491-508 (doi: 10.1080/10618600.2000.10474895
 (https://doi.org/10.1080/10618600.2000.10474895)).
 
    Nested lexically scoped functions also imply a further major difference.
@@ -911,12 +913,12 @@
 uses it to store the objects.  R performs its own memory management of this
 piece of memory, growing and shrinking its size as needed.  Having
 everything in memory is necessary because it is not really possible to
-externally maintain all relevant “environments” of symbol/value pairs.  This
+externally maintain all relevant "environments" of symbol/value pairs.  This
 difference also seems to make R _faster_ than S.
 
    The down side is that if R crashes you will lose all the work for the
-current session.  Saving and restoring the memory “images” (the functions
-and data stored in R’s internal memory at any time) can be a bit slow,
+current session.  Saving and restoring the memory "images" (the functions
+and data stored in R's internal memory at any time) can be a bit slow,
 especially if they are big.  In S this does not happen, because everything
 is saved in disk files and if you crash nothing is likely to happen to them.
 (In fact, one might conjecture that the S developers felt that the price of
@@ -956,8 +958,8 @@
 
 Apart from lexical scoping and its implications, R follows the S language
 definition in the Blue and White Books as much as possible, and hence really
-is an “implementation” of S. There are some intentional differences where
-the behavior of S is considered “not clean”.  In general, the rationale is
+is an "implementation" of S. There are some intentional differences where
+the behavior of S is considered "not clean".  In general, the rationale is
 that R should help you detect programming errors, while at the same time
 being as compatible as possible with S.
 
@@ -1032,7 +1034,7 @@
      the ‘dim’ attribute vector can be 0).  This has been determined a
      useful feature as it helps reducing the need for special-case tests for
      empty subsets.  For example, if ‘x’ is a matrix, ‘x[, FALSE]’ is not
-     ‘NULL’ but a “matrix” with 0 columns.  Hence, such objects need to be
+     ‘NULL’ but a "matrix" with 0 columns.  Hence, such objects need to be
      tested for by checking whether their ‘length()’ is zero (which works in
      both R and S), and not using ‘is.null()’.
 
@@ -1054,7 +1056,7 @@
    • In S, ‘substitute()’ searches for names for substitution in the given
      expression in three places: the actual and the default arguments of the
      matching call, and the local frame (in that order).  R looks in the
-     local frame only, with the special rule to use a “promise” if a
+     local frame only, with the special rule to use a "promise" if a
      variable is not evaluated.  Since the local frame is initialized with
      the actual arguments or the default expressions, this is usually
      equivalent to S, until assignment takes place.
@@ -1075,7 +1077,7 @@
      ‘Sys.setlocale()’ function.
 
    • In S, ‘missing(ARG)’ remains ‘TRUE’ if ARG is subsequently modified; in
-     R it doesn’t.
+     R it doesn't.
 
    • From R version 1.3.0, ‘data.frame’ strips ‘I()’ when creating (column)
      names.
@@ -1098,9 +1100,9 @@
      ‘$’ allow partial matches).  In S, ‘[’ allows partial matches.
 
    • S has a two-argument version of ‘atan’ and no ‘atan2’.  A call in S
-     such as ‘atan(x1, x2)’ is equivalent to R’s ‘atan2(x1, x2)’.  However,
-     beware of named arguments since S’s ‘atan(x = a, y = b)’ is equivalent
-     to R’s ‘atan2(y = a, x = b)’ with the meanings of ‘x’ and ‘y’
+     such as ‘atan(x1, x2)’ is equivalent to R's ‘atan2(x1, x2)’.  However,
+     beware of named arguments since S's ‘atan(x = a, y = b)’ is equivalent
+     to R's ‘atan2(y = a, x = b)’ with the meanings of ‘x’ and ‘y’
      interchanged.  (R used to have undocumented support for a two-argument
      ‘atan’ with positional arguments, but this has been withdrawn to avoid
      further confusion.)
@@ -1119,7 +1121,7 @@
 
 Since almost anything you can do in R has source code that you could port to
 S-PLUS with little effort there will never be much you can do in R that you
-couldn’t do in S-PLUS if you wanted to.  (Note that using lexical scoping
+couldn't do in S-PLUS if you wanted to.  (Note that using lexical scoping
 may simplify matters considerably, though.)
 
    R offers several graphics features that S-PLUS does not, such as finer
@@ -1127,9 +1129,9 @@
 correction for color, and, most importantly, mathematical annotation in plot
 texts, via input expressions reminiscent of TeX constructs.  See the help
 page for ‘plotmath’, which features an impressive on-line example.  More
-details can be found in Paul Murrell and Ross Ihaka (2000), “An Approach to
-Providing Mathematical Annotation in Plots”, _Journal of Computational and
-Graphical Statistics_, *9*, 582–599 (doi: 10.1080/10618600.2000.10474900
+details can be found in Paul Murrell and Ross Ihaka (2000), "An Approach to
+Providing Mathematical Annotation in Plots", _Journal of Computational and
+Graphical Statistics_, *9*, 582-599 (doi: 10.1080/10618600.2000.10474900
 (https://doi.org/10.1080/10618600.2000.10474900)).
 
 3.5 What is R-plus?
@@ -1149,17 +1151,17 @@
 4 R Web Interfaces
 ******************
 
-Please refer to the CRAN task view on “Web Technologies and Services”
+Please refer to the CRAN task view on "Web Technologies and Services"
 (<https://CRAN.R-project.org/view=WebTechnologies>), specifically section
-“Web and Server Frameworks”, for up-to-date information on R web interface
+"Web and Server Frameworks", for up-to-date information on R web interface
 packages.
 
-   Early references on R web interfaces include Jeff Banfield (1999), “Rweb:
-Web-based Statistical Analysis” (doi: 10.18637/jss.v004.i01
-(https://doi.org/10.18637/jss.v004.i01)), David Firth (2003), “CGIwithR:
-Facilities for processing web forms using R” (doi: 10.18637/jss.v008.i10
+   Early references on R web interfaces include Jeff Banfield (1999), "Rweb:
+Web-based Statistical Analysis" (doi: 10.18637/jss.v004.i01
+(https://doi.org/10.18637/jss.v004.i01)), David Firth (2003), "CGIwithR:
+Facilities for processing web forms using R" (doi: 10.18637/jss.v008.i10
 (https://doi.org/10.18637/jss.v008.i10)), and Angelo Mineo and Alfredo
-Pontillo (2006), “Using R via PHP for Teaching Purposes: R-php”
+Pontillo (2006), "Using R via PHP for Teaching Purposes: R-php"
 (doi: 10.18637/jss.v017.i04 (https://doi.org/10.18637/jss.v017.i04)).
 
 5 R Add-On Packages
@@ -1214,15 +1216,15 @@
 
 *KernSmooth*
      Functions for kernel smoothing (and density estimation) corresponding
-     to the book “Kernel Smoothing” by M. P. Wand and M. C. Jones, 1995.
+     to the book "Kernel Smoothing" by M. P. Wand and M. C. Jones, 1995.
 *MASS*
      Functions and datasets from the main package of Venables and Ripley,
-     “Modern Applied Statistics with S”.
+     "Modern Applied Statistics with S".
 *Matrix*
      Support for spares and dense matrices
 *boot*
-     Functions and datasets for bootstrapping from the book “Bootstrap
-     Methods and Their Applications” by A. C. Davison and D. V. Hinkley,
+     Functions and datasets for bootstrapping from the book "Bootstrap
+     Methods and Their Applications" by A. C. Davison and D. V. Hinkley,
      1997, Cambridge University Press.
 *class*
      Functions for classification (k-nearest neighbor and LVQ).
@@ -1241,13 +1243,13 @@
 *nlme*
      Fit and compare Gaussian linear and nonlinear mixed-effects models.
 *nnet*
-     Software for single hidden layer perceptrons (“feed-forward neural
-     networks”), and for multinomial log-linear models.
+     Software for single hidden layer perceptrons ("feed-forward neural
+     networks"), and for multinomial log-linear models.
 *rpart*
      Recursive PARTitioning and regression trees.
 *spatial*
-     Functions for kriging and point pattern analysis from “Modern Applied
-     Statistics with S” by W. Venables and B. Ripley.
+     Functions for kriging and point pattern analysis from "Modern Applied
+     Statistics with S" by W. Venables and B. Ripley.
 *survival*
      Functions for survival analysis, including penalized likelihood.
    See the CRAN contributed packages page for more information.
@@ -1356,7 +1358,7 @@
           tools         Tools for Package Development
           utils         The R Utils Package
 
-   You can “load” the installed package PKG by
+   You can "load" the installed package PKG by
 
      library(PKG)
 
@@ -1396,7 +1398,7 @@
 contain files ‘INDEX’, ‘NAMESPACE’, ‘configure’, ‘cleanup’, ‘LICENSE’,
 ‘LICENCE’, ‘COPYING’ and ‘NEWS’.
 
-   See section “Creating R packages” in ‘Writing R Extensions’, for details.
+   See section "Creating R packages" in ‘Writing R Extensions’, for details.
 This manual is included in the R distribution, *note What documentation
 exists for R?::, and gives information on package structure, the configure
 and cleanup mechanisms, and on automated package checking and building.
@@ -1426,7 +1428,7 @@
 6.1 Is there Emacs support for R?
 =================================
 
-There is an Emacs package called ESS (“Emacs Speaks Statistics”) which
+There is an Emacs package called ESS ("Emacs Speaks Statistics") which
 provides a standard interface between statistical programs and statistical
 processes.  It is intended to provide assistance for interactive statistical
 programming and data analysis.  Languages supported include: S dialects (R,
@@ -1471,7 +1473,7 @@
 
 Yes, instead of just running it in a console, _definitely_.  As an
 alternative to other IDEs such as RStudio, _possibly_, notably if you are
-interested to use Emacs for other computer interaction.  You’d be using ESS,
+interested to use Emacs for other computer interaction.  You'd be using ESS,
 Emacs Speaks Statistics, see previous FAQ.
 
    Inferior R mode provides a readline/history mechanism, object name
@@ -1494,7 +1496,7 @@
 6.3 Debugging R from within Emacs
 =================================
 
-To debug R “from within Emacs”, there are several possibilities.  To use the
+To debug R "from within Emacs", there are several possibilities.  To use the
 Emacs GUD (Grand Unified Debugger) library with the recommended debugger
 GDB, type ‘M-x gdb’ and give the path to the R _binary_ as argument.  At the
 ‘gdb’ prompt, set ‘R_HOME’ and other environment variables as needed (using
@@ -1547,7 +1549,7 @@
 7.2 How can I save my workspace?
 ================================
 
-‘save.image()’ saves the objects in the user’s ‘.GlobalEnv’ to the file
+‘save.image()’ saves the objects in the user's ‘.GlobalEnv’ to the file
 ‘.RData’ in the R startup directory.  (This is also what happens after
 ‘q("yes")’.)  Using ‘save.image(FILE)’ one can save the image under a
 different name.
@@ -1574,14 +1576,14 @@
    This is because in both cases, the first argument is evaluated in the
 calling environment first.  The result (which should be an object of mode
 ‘"expression"’ or ‘"call"’) is then evaluated or differentiated.  What you
-(most likely) really want is obtained by “quoting” the first argument upon
+(most likely) really want is obtained by "quoting" the first argument upon
 surrounding it with ‘expression()’.  For example,
 
      R> D(expression(x^2), "x")
      2 * x
 
    Although this behavior may initially seem to be rather strange, it is
-perfectly logical.  The “intuitive” behavior could easily be implemented,
+perfectly logical.  The "intuitive" behavior could easily be implemented,
 but problems would arise whenever the expression is contained in a variable,
 passed as a parameter, or is the result of a function call.  Consider for
 instance the semantics in cases like
@@ -1631,7 +1633,7 @@
 PKG)’, where NAME and PKG are strings giving the names of an object and the
 package containing it, stores some information in this environment.  When R
 tries to evaluate NAME, it loads the corresponding package PKG and
-reevaluates NAME in the new package’s environment.
+reevaluates NAME in the new package's environment.
 
    Using this mechanism makes R behave as if the package was loaded, but
 does not occupy memory (yet).
@@ -1642,10 +1644,10 @@
 =============================
 
 The function ‘options()’ allows setting and examining a variety of global
-“options” which affect the way in which R computes and displays its results.
+"options" which affect the way in which R computes and displays its results.
 The variable ‘.Options’ holds the current values of these options, but
 should never directly be assigned to unless you want to drive yourself
-crazy—simply pretend that it is a “read-only” variable.
+crazy--simply pretend that it is a "read-only" variable.
 
    For example, given
 
@@ -1686,7 +1688,7 @@
 This is about a problem rarely seen with modern X11 installations.
 
    On an X11 device, plotting sometimes, e.g., when running ‘demo("image")’,
-results in “Error: color allocation error”.  This is an X problem, and only
+results in "Error: color allocation error".  This is an X problem, and only
 indirectly related to R. It occurs when applications started prior to R have
 used all the available colors.  (How many colors are available depends on
 the X configuration; sometimes only 256 colors can be used.)
@@ -1722,18 +1724,18 @@
    You could also look at ‘coplot()’ and ‘dotchart()’ which might do at
 least some of what you want.  Note also that the R version of ‘pairs()’ is
 fairly general and provides most of the functionality of ‘splom()’, and that
-R’s default plot method has an argument ‘asp’ allowing to specify (and fix
+R's default plot method has an argument ‘asp’ allowing to specify (and fix
 against device resizing) the aspect ratio of the plot.
 
-   (Because the word “Trellis” has been claimed as a trademark we do not use
-it in R. The name “lattice” has been chosen for the R equivalent.)
+   (Because the word "Trellis" has been claimed as a trademark we do not use
+it in R. The name "lattice" has been chosen for the R equivalent.)
 
 7.12 What are the enclosing and parent environments?
 ====================================================
 
 Inside a function you may want to access variables in two additional
-environments: the one that the function was defined in (“enclosing”), and
-the one it was invoked in (“parent”).
+environments: the one that the function was defined in ("enclosing"), and
+the one it was invoked in ("parent").
 
    If you create a function at the command line or load it in a package its
 enclosing environment is the global workspace.  If you define a function
@@ -1742,7 +1744,7 @@
 when the function is created.  You can find out the enclosing environment
 for a function ‘f()’ using ‘environment(f)’.
 
-   The “parent” environment, on the other hand, is defined when you invoke a
+   The "parent" environment, on the other hand, is defined when you invoke a
 function.  If you invoke ‘lm()’ at the command line its parent environment
 is the global workspace, if you invoke it inside a function ‘f()’ then its
 parent environment is the environment inside ‘f()’.  You can find out the
@@ -1758,7 +1760,7 @@
 
    Parent environments are important because things like model formulas need
 to be evaluated in the environment the function was called from, since
-that’s where all the variables will be available.  This relies on the parent
+that's where all the variables will be available.  This relies on the parent
 environment being potentially different with each invocation.
 
    Enclosing environments are important because a function can use variables
@@ -1804,8 +1806,8 @@
 argument ‘check.names’ to these functions controls whether variable names
 are checked and adjusted by ‘make.names()’ if needed.)
 
-   To understand what names are “valid”, one needs to take into account that
-the term “name” is used in several different (but related) ways in the
+   To understand what names are "valid", one needs to take into account that
+the term "name" is used in several different (but related) ways in the
 language:
 
   1. A _syntactic name_ is a string the parser interprets as this type of
@@ -1833,7 +1835,7 @@
   5. Finally, a _file name_ is a string identifying a file in the operating
      system for reading, writing, etc.  It really has nothing much to do
      with names in the language, but it is traditional to call these strings
-     file “names”.
+     file "names".
 
 7.15 Are GAMs implemented in R?
 ===============================
@@ -1868,7 +1870,7 @@
    If you type ‘1+1’ or ‘summary(glm(y~x+z, family=binomial))’ at the
 command line the returned value is automatically printed (unless it is
 ‘invisible()’), but in other circumstances, such as in a ‘source()’d file or
-inside a function it isn’t printed unless you specifically print it.
+inside a function it isn't printed unless you specifically print it.
 
    To print the value use
 
@@ -1925,7 +1927,7 @@
 
    Some packages report instead the sums of squares based on comparing the
 full model to the models with each factor removed one at a time (the famous
-‘Type III sums of squares’ from SAS, for example).  These do not depend on
+'Type III sums of squares' from SAS, for example).  These do not depend on
 the order of factors in the model.  The question of which set of sums of
 squares is the Right Thing provokes low-level holy wars on R-help from time
 to time.
@@ -1958,7 +1960,7 @@
 The Unix-like command-line interface to R can only provide the inbuilt
 command line editor which allows recall, editing and re-submission of prior
 commands provided that the GNU readline library is available at the time R
-is configured for compilation.  Note that the ‘development’ version of
+is configured for compilation.  Note that the 'development' version of
 readline including the appropriate headers is needed: users of Linux binary
 distributions will need to install packages such as ‘libreadline-dev’
 (Debian) or ‘readline-devel’ (Red Hat).
@@ -2063,8 +2065,8 @@
      getS3method("[", "terms")
 
 To see the code for an unexported function ‘foo()’ in the namespace of
-package ‘"bar"’ use ‘bar:::foo’.  Don’t use these constructions to call
-unexported functions in your own code—they are probably unexported for a
+package ‘"bar"’ use ‘bar:::foo’.  Don't use these constructions to call
+unexported functions in your own code--they are probably unexported for a
 reason and may change without warning.
 
 7.27 How can I create rotated axis labels?
@@ -2094,8 +2096,8 @@
 x axis.  See ‘?par’ for more information.
 
    Also see Figure 1 and associated code in Paul Murrell (2003),
-“Integrating grid Graphics Output with Base Graphics Output”, _R News_,
-*3/2*, 7–12.
+"Integrating grid Graphics Output with Base Graphics Output", _R News_,
+*3/2*, 7-12.
 
 7.28 Why is read.table() so inefficient?
 ========================================
@@ -2112,12 +2114,12 @@
 A “package” is a standardized collection of material extending R, e.g.
 providing code, data, or documentation.  A “library” is a place (directory)
 where R knows to find packages it can use (i.e., which were “installed”).  R
-is told to use a package (to “load” it and add it to the search path) via
+is told to use a package (to "load" it and add it to the search path) via
 calls to the function ‘library’.  I.e., ‘library()’ is employed to load a
 package from libraries containing packages.
 
    *Note R Add-On Packages::, for more details.  See also Uwe Ligges (2003),
-“R Help Desk: Package Management”, _R News_, *3/3*, 37–39.
+"R Help Desk: Package Management", _R News_, *3/3*, 37-39.
 
 7.30 I installed a package but the functions are not there
 ==========================================================
@@ -2127,10 +2129,10 @@
    See *note R Add-On Packages:: and *note What is the difference between
 package and library?:: for more information.
 
-7.31 Why doesn’t R think these numbers are equal?
+7.31 Why doesn't R think these numbers are equal?
 =================================================
 
-The only numbers that can be represented exactly in R’s numeric type are
+The only numbers that can be represented exactly in R's numeric type are
 integers and fractions whose denominator is a power of 2.  All other numbers
 are internally rounded to (typically) 53 binary digits accuracy.  As a
 result, two floating point numbers will not reliably be equal unless they
@@ -2150,15 +2152,15 @@
 you will need to consider error propagation carefully.
 
    A discussion with many easily followed examples is in Appendix G
-“Computational Precision and Floating Point Arithmetic”, pages 753–771 of
+"Computational Precision and Floating Point Arithmetic", pages 753-771 of
 _Statistical Analysis and Data Display: An Intermediate Course with Examples
 in R_, Richard M. Heiberger and Burt Holland (Springer 2015, second
 edition).  This appendix is a free download from
 <https://link.springer.com/content/pdf/bbm:978-1-4939-2122-5/1.pdf>.
 
-   For more information, see e.g. David Goldberg (1991), “What Every
-Computer Scientist Should Know About Floating-Point Arithmetic”, _ACM
-Computing Surveys_, *23/1*, 5–48, also available via
+   For more information, see e.g. David Goldberg (1991), "What Every
+Computer Scientist Should Know About Floating-Point Arithmetic", _ACM
+Computing Surveys_, *23/1*, 5-48, also available via
 <https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html>.
 
    Here is another example, this time using addition:
@@ -2363,8 +2365,8 @@
 
 In most cases, typing the name of the function will print its source code.
 However, code is sometimes hidden in a namespace, or compiled.  For a
-complete overview on how to access source code, see Uwe Ligges (2006), “Help
-Desk: Accessing the sources”, _R News_, *6/4*, 43–45
+complete overview on how to access source code, see Uwe Ligges (2006), "Help
+Desk: Accessing the sources", _R News_, *6/4*, 43-45
 (<https://CRAN.R-project.org/doc/Rnews/Rnews_2006-4.pdf>).
 
 7.41 Why does summary() report strange results for the R^2 estimate when I fit a linear model with no intercept?
@@ -2383,17 +2385,17 @@
      a line through the origin.
 
    All these come down to saying that if you know _a priori_ that E[Y]=0
-when x=0 then the ‘null’ model that you should compare to the fitted line,
-the model where x doesn’t explain any of the variance, is the model where
-E[Y]=0 everywhere.  (If you don’t know a priori that E[Y]=0 when x=0, then
-you probably shouldn’t be fitting a line through the origin.)
+when x=0 then the 'null' model that you should compare to the fitted line,
+the model where x doesn't explain any of the variance, is the model where
+E[Y]=0 everywhere.  (If you don't know a priori that E[Y]=0 when x=0, then
+you probably shouldn't be fitting a line through the origin.)
 
 7.42 Why is R apparently not releasing memory?
 ==============================================
 
-This question is often asked in different flavors along the lines of “I have
+This question is often asked in different flavors along the lines of "I have
 removed objects in R and run ‘gc()’ and yet ‘ps’/‘top’ still shows the R
-process using a lot of memory”, often on Linux machines.
+process using a lot of memory", often on Linux machines.
 
    This is an artifact of the way the operating system (OS) allocates
 memory.  In general it is common that the OS is not capable of releasing all
@@ -2419,7 +2421,7 @@
 regions.  For smaller allocations the system can expand the data segment of
 the process (historically using the ‘brk’ system call), but this whole area
 is always contiguous.  The OS can only move the end of this space, it cannot
-create any “holes”.  Since this operation is fairly cheap, it is used for
+create any "holes".  Since this operation is fairly cheap, it is used for
 allocations of small pieces of memory.  However, the side-effect is that
 even if there is just one byte that is in use at the end of the data
 segment, the OS cannot release any memory at all, because it cannot change
@@ -2456,7 +2458,7 @@
 Since March 2016, Windows and macOS binaries of CRAN packages for old
 versions of R (released more than 5 years ago) are made available from a
 central CRAN archive server instead of the CRAN mirrors.  To get these, one
-should set the CRAN “mirror” element of the ‘repos’ option accordingly, by
+should set the CRAN "mirror" element of the ‘repos’ option accordingly, by
 something like
      local({r <- getOption("repos")
             r["CRAN"] <- "http://CRAN-archive.R-project.org"
@@ -2477,7 +2479,7 @@
 This approach is preferred over having ‘summary.foo()’ print summary
 information and return something useful, as sometimes you need to grab
 something computed by ‘summary()’ inside a function or similar.  In such
-cases you don’t want anything printed.
+cases you don't want anything printed.
 
 8.2 How can I debug dynamically loaded code?
 ============================================
@@ -2485,7 +2487,7 @@
 Roughly speaking, you need to start R inside the debugger, load the code,
 send an interrupt, and then set the required breakpoints.
 
-   See section “Finding entry points in dynamically loaded code” in ‘Writing
+   See section "Finding entry points in dynamically loaded code" in ‘Writing
 R Extensions’.  This manual is included in the R distribution, *note What
 documentation exists for R?::.
 
@@ -2494,7 +2496,7 @@
 
 The most convenient way is to call ‘R_PV’ from the symbolic debugger.
 
-   See section “Inspecting R objects when debugging” in ‘Writing R
+   See section "Inspecting R objects when debugging" in ‘Writing R
 Extensions’.
 
 8.4 How can I change compilation flags?
@@ -2506,7 +2508,7 @@
 
    Starting with R 2.1.0, users can provide personal ‘Makevars’
 configuration files in ‘$HOME/.R’ to override the default flags.  See
-section “Add-on packages” in ‘R Installation and Administration’.
+section "Add-on packages" in ‘R Installation and Administration’.
 
 8.5 How can I debug S4 methods?
 ===============================
@@ -2523,31 +2525,31 @@
 
 If R executes an illegal instruction, or dies with an operating system error
 message that indicates a problem in the program (as opposed to something
-like “disk full”), then it is certainly a bug.  If you call ‘.C()’,
+like "disk full"), then it is certainly a bug.  If you call ‘.C()’,
 ‘.Fortran()’, ‘.External()’ or ‘.Call()’ (or ‘.Internal()’) yourself (or in
 a function you wrote), you can always crash R by using wrong argument types
 (modes).  This is not a bug.
 
    Taking forever to complete a command can be a bug, but you must make
-certain that it was really R’s fault.  Some commands simply take a long
+certain that it was really R's fault.  Some commands simply take a long
 time.  If the input was such that you _know_ it should have been processed
-quickly, report a bug.  If you don’t know whether the command should take a
+quickly, report a bug.  If you don't know whether the command should take a
 long time, find out by looking in the manual or by asking for assistance.
 
    If a command you are familiar with causes an R error message in a case
 where its usual definition ought to be reasonable, it is probably a bug.  If
 a command does the wrong thing, that is a bug.  But be sure you know for
-certain what it ought to have done.  If you aren’t familiar with the
-command, or don’t know for certain how the command is supposed to work, then
+certain what it ought to have done.  If you aren't familiar with the
+command, or don't know for certain how the command is supposed to work, then
 it might actually be working right.  For example, people sometimes think
-there is a bug in R’s mathematics because they don’t understand how
+there is a bug in R's mathematics because they don't understand how
 finite-precision arithmetic works.  Rather than jumping to conclusions, show
 the problem to someone who knows for certain.  Unexpected results of
 comparison of decimal numbers, for example ‘0.28 * 100 != 28’ or ‘0.1 + 0.2
 != 0.3’, are not a bug.  *Note Why doesn't R think these numbers are
 equal?::, for more details.
 
-   Finally, a command’s intended definition may not be best for statistical
+   Finally, a command's intended definition may not be best for statistical
 analysis.  This is a very important sort of problem, but it is also a matter
 of judgment.  Also, it is easy to come to such a conclusion out of ignorance
 of some of the existing features.  It is probably best not to complain about
@@ -2555,15 +2557,15 @@
 feel confident that you understand it, and know for certain that what you
 want is not available.  If you are not sure what the command is supposed to
 do after a careful reading of the manual this indicates a bug in the manual.
-The manual’s job is to make everything clear.  It is just as important to
+The manual's job is to make everything clear.  It is just as important to
 report documentation bugs as program bugs.  However, we know that the
-introductory documentation is seriously inadequate, so you don’t need to
+introductory documentation is seriously inadequate, so you don't need to
 report this.
 
    If the online argument list of a function disagrees with the manual, one
 of them must be wrong, so report the bug.
 
-   See also “Making sure it’s a bug” in Bug Reporting in R
+   See also "Making sure it's a bug" in Bug Reporting in R
 (https://www.r-project.org/bugs.html) for more information.
 
 9.2 How to report a bug
@@ -2597,7 +2599,7 @@
 guess that they should try a day of the week variable name.
 
    Or perhaps the command fails because the last command you used was a
-method for ‘"["()’ that had a bug causing R’s internal data structures to be
+method for ‘"["()’ that had a bug causing R's internal data structures to be
 corrupted and making the ‘data.frame()’ command fail from then on.  This is
 why others need to know what other commands you have typed (or read from
 your startup file).
@@ -2615,8 +2617,8 @@
 ensures that the site profile and saved data files are not read.
 
    Before you actually submit a bug report, you should check whether the bug
-has already been reported and/or fixed.  First, try the “Show open bugs
-new-to-old” or the search facility on <https://bugs.R-project.org/>.
+has already been reported and/or fixed.  First, try the "Show open bugs
+new-to-old" or the search facility on <https://bugs.R-project.org/>.
 Second, consult <https://svn.R-project.org/R/trunk/doc/NEWS.Rd>, which
 records changes that will appear in the _next_ release of R, including bug
 fixes that do not appear on the Bug Tracker.  Third, if possible try the
@@ -2630,10 +2632,10 @@
    A bug report can be generated using the function ‘bug.report()’.  For
 reports on R this will open the R Bugzilla page at
 <https://bugs.R-project.org/>: for a contributed package it will open the
-package’s bug tracker Web page or help you compose an email to the
-maintainer.  Since 2016, only “members” (including all who have previously
-submitted bugs) can submit new bugs on the R Bugzilla.  See “Where to submit
-bug reports and patches” on Bug Reporting in R
+package's bug tracker Web page or help you compose an email to the
+maintainer.  Since 2016, only "members" (including all who have previously
+submitted bugs) can submit new bugs on the R Bugzilla.  See "Where to submit
+bug reports and patches" on Bug Reporting in R
 (https://www.r-project.org/bugs.html) for more information.
 
    There is a section of the bug repository for suggestions for enhancements
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/NEWS R-patched/doc/NEWS
--- R-release-orig/doc/NEWS	2024-06-14 09:05:24.000000000 +0200
+++ R-patched/doc/NEWS	2024-10-19 01:35:18.231226026 +0200
@@ -1,5 +1,37 @@
 R News
 
+CHANGES IN R 4.4.1 patched:
+
+  C-LEVEL FACILITIES:
+
+    * The S-compatibility macros F77_COM and F77_COMDECL defined in
+      header R_ext/RS.h are deprecated and will be removed shortly.  We
+      could find no record of their use.
+
+  BUG FIXES:
+
+    * Mathlib function lgammacor(x) no longer warns about underflow to
+      zero for large x.
+
+    * Text widths and heights were incorrectly reported by the Quartz
+      device if the drawing context didn't exist yet (typically when
+      drawing off-screen to a window that is yet to appear, see
+      PR#18591).
+
+    * The Quartz device could segfault in cases where paths with spaces
+      are used in the new glyph drawing API.  Thanks to Tomek
+      Gieorgijewski (PR#18758).
+
+    * On macOS in R CRAN builds, it is again possible to read
+      little-endian UTF-16 text with a BOM from a connection using
+      encoding="UTF-16".  Users building R from source should avoid
+      using the system libiconv in macOS 14.1 and later.
+
+    * methods' internal .requirePackage() now re-enables primitive
+      method dispatch when needed; thanks to Ivan Krylov for
+      demystifying CRAN package check failures on the R*devel mailing
+      lists.
+
 CHANGES IN R 4.4.1:
 
   C-LEVEL FACILITIES:
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/NEWS.Rd R-patched/doc/NEWS.Rd
--- R-release-orig/doc/NEWS.Rd	2024-06-04 00:04:01.000000000 +0200
+++ R-patched/doc/NEWS.Rd	2024-10-13 01:31:06.300855528 +0200
@@ -5,6 +5,42 @@
 \title{R News}
 \encoding{UTF-8}
 
+\section{\Rlogo CHANGES IN R 4.4.1 patched}{
+  \subsection{C-LEVEL FACILITIES}{
+    \itemize{
+      \item The S-compatibility macros \code{F77_COM} and
+      \code{F77_COMDECL} defined in header \file{R_ext/RS.h} are
+      deprecated and will be removed shortly.  We could find no record
+      of their use.
+    }
+  }
+  \subsection{BUG FIXES}{
+    \itemize{
+      \item \I{Mathlib} function \code{lgammacor(x)} no longer warns about
+      underflow to zero for large \code{x}.
+
+      \item Text widths and heights were incorrectly reported by the
+      Quartz device if the drawing context didn't exist yet (typically
+      when drawing off-screen to a window that is yet to appear, see
+      \PR{18591}).
+
+      \item The Quartz device could segfault in cases where paths with
+      spaces are used in the new glyph drawing API.
+      Thanks to \I{Tomek Gieorgijewski} (\PR{18758}).
+
+      \item On macOS in R CRAN builds, it is again possible to read
+      little-endian UTF-16 text with a BOM from a connection using
+      \code{encoding="UTF-16"}.  Users building R from source should avoid
+      using the system libiconv in macOS 14.1 and later.
+
+      \item \pkg{methods}' internal \code{.requirePackage()} now re-enables
+      primitive method dispatch when needed; thanks to \I{Ivan Krylov}
+      for demystifying CRAN package check failures on the R*devel mailing
+      lists.
+    }
+  }
+}
+
 \section{\Rlogo CHANGES IN R 4.4.1}{
   \subsection{C-LEVEL FACILITIES}{
     \itemize{
Binary files R-release-orig/doc/NEWS.pdf and R-patched/doc/NEWS.pdf differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/RESOURCES R-patched/doc/RESOURCES
--- R-release-orig/doc/RESOURCES	2024-06-14 09:02:21.000000000 +0200
+++ R-patched/doc/RESOURCES	2024-10-19 01:32:16.664562729 +0200
@@ -1,5 +1,5 @@
 
-                            AVAILABLE R RESOURCES
+ AVAILABLE R RESOURCES
 
 1 FAQ
 *****
@@ -9,9 +9,9 @@
 
      <https://CRAN.R-project.org/doc/FAQ/R-FAQ.html>
 
-A text version is in file 'FAQ' in this directory, and an HTML version is
-available as file 'doc/html/faq.html' and via the on-line help (on the index
-page given by 'help.start()').
+A text version is in file ‘FAQ’ in this directory, and an HTML version is
+available as file ‘doc/html/faq.html’ and via the on-line help (on the index
+page given by ‘help.start()’).
 
 2 Mailing lists
 ***************
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/html/NEWS.html R-patched/doc/html/NEWS.html
--- R-release-orig/doc/html/NEWS.html	2024-06-14 09:05:24.000000000 +0200
+++ R-patched/doc/html/NEWS.html	2024-10-19 01:35:20.287837606 +0200
@@ -18,6 +18,59 @@
 
 <h2>R News</h2>
 
+<h3><img src="../help/figures/../../html/Rlogo.svg" class="toplogo" alt="[R logo]" /> CHANGES IN R 4.4.1 patched</h3>
+
+
+
+<h4>C-LEVEL FACILITIES</h4>
+
+
+<ul>
+<li><p> The S-compatibility macros <code>F77_COM</code> and
+<code>F77_COMDECL</code> defined in header &lsquo;<span class="file">R_ext/RS.h</span>&rsquo; are
+deprecated and will be removed shortly.  We could find no record
+of their use.
+</p>
+</li></ul>
+
+
+
+
+<h4>BUG FIXES</h4>
+
+
+<ul>
+<li> <p>Mathlib function <code>lgammacor(x)</code> no longer warns about
+underflow to zero for large <code>x</code>.
+</p>
+</li>
+<li><p> Text widths and heights were incorrectly reported by the
+Quartz device if the drawing context didn't exist yet (typically
+when drawing off-screen to a window that is yet to appear, see
+<a href="https://bugs.R-project.org/show_bug.cgi?id=18591">PR#18591</a>).
+</p>
+</li>
+<li><p> The Quartz device could segfault in cases where paths with
+spaces are used in the new glyph drawing API.
+Thanks to Tomek Gieorgijewski (<a href="https://bugs.R-project.org/show_bug.cgi?id=18758">PR#18758</a>).
+</p>
+</li>
+<li><p> On macOS in R CRAN builds, it is again possible to read
+little-endian UTF-16 text with a BOM from a connection using
+<code>encoding="UTF-16"</code>.  Users building R from source should avoid
+using the system libiconv in macOS 14.1 and later.
+</p>
+</li>
+<li> <p><span class="pkg">methods</span>' internal <code>.requirePackage()</code> now re-enables
+primitive method dispatch when needed; thanks to Ivan Krylov
+for demystifying CRAN package check failures on the R*devel mailing
+lists.
+</p>
+</li></ul>
+
+
+
+
 <h3><img src="../help/figures/../../html/Rlogo.svg" class="toplogo" alt="[R logo]" /> CHANGES IN R 4.4.1</h3>
 
 
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/html/R-admin.html R-patched/doc/html/R-admin.html
--- R-release-orig/doc/html/R-admin.html	2024-06-14 09:08:02.000000000 +0200
+++ R-patched/doc/html/R-admin.html	2024-10-19 01:43:39.473885698 +0200
@@ -1,11 +1,11 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE html>
 <html>
-
+
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-
+
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 <title>R Resources</title>
@@ -18,21 +18,8 @@
 <link href="dir.html#Top" rel="prev" title="(dir)">
 <style type="text/css">
 <!--
-a.copiable-anchor {visibility: hidden; text-decoration: none; line-height: 0em}
-a.summary-letter {text-decoration: none}
-blockquote.indentedblock {margin-right: 0em}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-kbd {font-style: oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-span.nolinebreak {white-space: nowrap}
-span.roman {font-family: initial; font-weight: normal}
-span.sansserif {font-family: sans-serif; font-weight: normal}
-span:hover a.copiable-anchor {visibility: visible}
-ul.no-bullet {list-style: none}
+a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
+span:hover a.copiable-link {visibility: visible}
 @media screen {
     .container {
 	padding-right: 10px;
@@ -171,7 +158,6 @@
 </head>
 
 <body lang="en">
-<h1 class="settitle" align="center">R Resources</h1>
 
 
 
@@ -181,62 +167,62 @@
 </h1>
 <hr>
 
-<span id="Top"></span><h1 class="node-heading">Top</h1>
+<h1 class="node" id="Top"><span>Top<a class="copiable-link" href="#Top"> &para;</a></span></h1>
 
 
 <hr>
-<div class="chapter" id="FAQ">
-<span id="FAQ-1"></span><h3 class="section">1 FAQ</h3>
+<div class="section-level-extent" id="FAQ">
+<h3 class="section chapter-level-set-section" id="FAQ-1"><span>1 FAQ<a class="copiable-link" href="#FAQ-1"> &para;</a></span></h3>
 
-<p>A collection of <a href="faq.html">Frequently Asked Questions</a> and their
-answers is maintained by <a href="mailto:Kurt.Hornik@R-project.org">Kurt Hornik</a>
-and can be found at the <acronym>URL</acronym>
+<p>A collection of <a class="uref" href="faq.html">Frequently Asked Questions</a> and their
+answers is maintained by <a class="email" href="mailto:Kurt.Hornik@R-project.org">Kurt Hornik</a>
+and can be found at the <abbr class="acronym">URL</abbr>
 </p>
-<blockquote>
-<p><a href="https://CRAN.R-project.org/doc/FAQ/R-FAQ.html">https://CRAN.R-project.org/doc/FAQ/R-FAQ.html</a>
+<blockquote class="quotation">
+<p><a class="uref" href="https://CRAN.R-project.org/doc/FAQ/R-FAQ.html">https://CRAN.R-project.org/doc/FAQ/R-FAQ.html</a>
 </p></blockquote>
 
 
 <hr>
 </div>
-<div class="chapter" id="Mailing-lists">
-<span id="Mailing-lists-1"></span><h3 class="section">2 Mailing lists</h3>
+<div class="section-level-extent" id="Mailing-lists">
+<h3 class="section chapter-level-set-section" id="Mailing-lists-1"><span>2 Mailing lists<a class="copiable-link" href="#Mailing-lists-1"> &para;</a></span></h3>
 
-<p>Thanks to <a href="mailto:Martin.Maechler@R-project.org">Martin Maechler</a> there
+<p>Thanks to <a class="email" href="mailto:Martin.Maechler@R-project.org">Martin Maechler</a> there
 are a number of mailing lists which are used by R users and developers.
 See
 </p>
-<blockquote>
-<p><a href="https://www.R-project.org/mail.html">https://www.R-project.org/mail.html</a>
+<blockquote class="quotation">
+<p><a class="uref" href="https://www.R-project.org/mail.html">https://www.R-project.org/mail.html</a>
 </p></blockquote>
 
 <p>for details.
 </p>
 <hr>
 </div>
-<div class="chapter" id="Archives">
-<span id="Archives-1"></span><h3 class="section">3 Archives</h3>
+<div class="section-level-extent" id="Archives">
+<h3 class="section chapter-level-set-section" id="Archives-1"><span>3 Archives<a class="copiable-link" href="#Archives-1"> &para;</a></span></h3>
 
-<p>The Comprehensive R Archive Network (<acronym>CRAN</acronym>) is a collection of
+<p>The Comprehensive R Archive Network (<abbr class="acronym">CRAN</abbr>) is a collection of
 sites which carry identical material, consisting of the R
 distribution(s), the contributed extensions, documentation for R, and
-binaries, with the master site at <a href="https://CRAN.R-project.org/">https://CRAN.R-project.org/</a> and
+binaries, with the master site at <a class="uref" href="https://CRAN.R-project.org/">https://CRAN.R-project.org/</a> and
 information on daily mirrors available from
 </p>
-<blockquote>
-<p><a href="https://CRAN.R-project.org/mirrors.html">https://CRAN.R-project.org/mirrors.html</a>
+<blockquote class="quotation">
+<p><a class="uref" href="https://CRAN.R-project.org/mirrors.html">https://CRAN.R-project.org/mirrors.html</a>
 </p></blockquote>
 
 <hr>
 </div>
-<div class="chapter" id="Bug_002dtracking-system">
-<span id="Bug_002dtracking-system-1"></span><h3 class="section">4 Bug-tracking system</h3>
+<div class="section-level-extent" id="Bug_002dtracking-system">
+<h3 class="section chapter-level-set-section" id="Bug_002dtracking-system-1"><span>4 Bug-tracking system<a class="copiable-link" href="#Bug_002dtracking-system-1"> &para;</a></span></h3>
 
 <p>R has a bug-tracking system (or perhaps a bug-filing system is a more
 precise description) available on the net at
 </p>
-<blockquote>
-<p><a href="https://bugs.R-project.org/">https://bugs.R-project.org/</a>
+<blockquote class="quotation">
+<p><a class="uref" href="https://bugs.R-project.org/">https://bugs.R-project.org/</a>
 </p></blockquote>
 
 </div>
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/manual/R-FAQ.texi R-patched/doc/manual/R-FAQ.texi
--- R-release-orig/doc/manual/R-FAQ.texi	2024-05-01 00:15:01.000000000 +0200
+++ R-patched/doc/manual/R-FAQ.texi	2024-08-29 17:45:07.496770150 +0200
@@ -349,6 +349,8 @@
 
 Tarballs with daily snapshots of the r-devel and r-patched development
 versions of R can be found at
+@url{https://cran.r-project.org/src/base-prerelease}. An alternative
+source is
 @url{https://stat.ethz.ch/R/daily/}.
 
 @c Sources are also available via anonymous rsync.  Use
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/manual/R-admin.texi R-patched/doc/manual/R-admin.texi
--- R-release-orig/doc/manual/R-admin.texi	2024-06-02 00:15:00.000000000 +0200
+++ R-patched/doc/manual/R-admin.texi	2024-09-28 17:45:06.189194267 +0200
@@ -148,10 +148,13 @@
 Subversion.)
 
 The tarballs are available from
-@uref{https://stat.ethz.ch/R/daily/}.  Download
+@uref{https://cran.r-project.org/src/base-prerelease}.  Download
 @file{R-patched.tar.gz} or @file{R-devel.tar.gz} (or the @file{.tar.bz2}
 versions) and unpack as described in the previous section.  They are
-built in exactly the same way as distributions of @R{} releases.
+built in exactly the same way and on the same platform as distributions
+of @R{} releases. Notice, that you probably want to use the CRAN master
+site for this, due to propagation delays. An
+alternative source of daily snapshots is maintained at @uref{https://stat.ethz.ch/R/daily/}.
 
 @menu
 * Using Subversion and rsync::
@@ -1068,14 +1071,14 @@
          c++20 gnu++20 (from 10) c++23 gnu++23 c++2b gnu++2b (from 11)
 Intel:   c++11  gnu+11 c++14 gnu++14 c++17 gnu++17
          c++20 gnu++20 (from 2021.1) c++2b gnu++2b (from 2022.2)
+         c++23 gnu++23 (at least from 2024.0)
 @end example
 @noindent
 (Those for @I{LLVM} @command{clang++} are documented at
 @uref{https://clang.llvm.org/cxx_status.html}, and follow @code{g++}:
 @code{-std=c++20} is supported from Clang 10, @code{-std=c++2b} from
 Clang 13 and @code{-std=c++23} from Clang 17.  Apple Clang supports
-@code{-std=c++2b} from 13.1.6: version 15.0.0 does not support
-@code{-std=c++23}.)
+@code{-std=c++2b} from 13.1.6 and @code{-std=c++23} from 16.0.0.)
 
 @c c++1y does not pass the configure test in gcc 4.9.3
 @c , with @option{-std=c++1y} (introduced@footnote{See
@@ -5006,15 +5009,14 @@
 define @code{__INTEL_COMPILER}: they also define @code{__clang__} and
 @code{__clang_major__}).
 
-The C++ compiler uses the system's @code{lidstdc++} as its runtime
+The C++ compiler uses the system's @code{libstdc++} as its runtime
 library rather than @I{LLVM}'s @code{libc++}.
 
 Standalone installers (which are free-of-charge) are available from
 @uref{https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html}:
 they are also part of the @I{oneAPI} Base and HPC (for Fortran) toolkits.
 
-We tried the compilers in @I{oneAPI} 2024.1.x@footnote{2024.1.2 for
-C/C++, 2024.1.0 for Fortran.} and 2023.x.y using (the paths
+We tried the compilers in @I{oneAPI} 2024.2.1 and 2023.x.y using (the paths
 do differ by compiler version)
 @example
 IP=/path/to/compilers/bin/
@@ -5066,7 +5068,7 @@
 @abbr{LTO}: it is not clear if the Fortran one does.
 
 @c https://community.intel.com/t5/Intel-C-Compiler/Troubles-with-getrusage-when-using-icx/m-p/1509374#M41116
-For some recent versions (including 2023.2.0) all CPU times in e.g.@:
+For some earlier versions (including 2023.2.0) all CPU times in e.g.@:
 @code{proc.time()} are reported as zero.  If you see this, uncomment the
 @samp{INTEL_ICX_FIX} setting in @file{config.site} and re-build.
 
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/manual/R-exts.texi R-patched/doc/manual/R-exts.texi
--- R-release-orig/doc/manual/R-exts.texi	2024-06-05 00:15:01.000000000 +0200
+++ R-patched/doc/manual/R-exts.texi	2024-09-15 17:45:06.355614150 +0200
@@ -2942,6 +2942,11 @@
 @end example
 
 @noindent
+Some maintainers have found it difficult to find @emph{all} the module
+dependencies which leads to hard-to-reproduce installation failures.
+There are tools available to find these, including the Intel compiler's
+flag @option{-gen-dep} and @code{makedepf90}.
+
 Note that it is not portable (although some platforms do accept it) to
 define a module of the same name in multiple source files.
 @c As was done by frailtypack in 2018-12: gfortran accepted this, ODS
@@ -3129,9 +3134,9 @@
 it will not apply to packages using @file{src/Makefile} or building in a
 subdirectory that do not set the C++ standard.  And compilers' default
 C++ standards varies widely and gets changed frequently by vendors --
-for example Apple clang up to at least 15 defaults to C++98, @I{LLVM}
+for example Apple clang up to at least 16 defaults to C++98, @I{LLVM}
 clang 14--15 to C++14, @I{LLVM} clang 16--18 to C++17 and @command{g++}
-11--13 to C++17.
+11--14 to C++17.
 
 For a package with a @file{src/Makefile} (or a Windows analogue),
 a non-default C++ compiler can be selected by including something like
@@ -3193,7 +3198,7 @@
 @subsection C standards
 
 C has had standards C89/C90, C99, C11, C17 (also known as C18), and C23
-is in final draft and expected to be published in early 2024.  C11 was a
+is in final draft and expected to be published in 2024.  C11 was a
 minor change to C99 which introduced some new features and made others
 optional, and C17 is a `bug-fix' update to C11.  On the other hand, C23
 makes extensive changes, including making @code{bool}, @code{true} and
@@ -4969,7 +4974,9 @@
 and ensure that you use the value of environment variable @env{MAKE}
 (and not just @command{make}) in your scripts.  (On some platforms GNU
 make is available under a name such as @command{gmake}, and there
-@code{SystemRequirements} is used to set @env{MAKE}.)
+@code{SystemRequirements} is used to set @env{MAKE}.)  Your
+@code{configure} script (or similar) does need to check that the
+executable pointed to by @env{MAKE} is indeed GNU make.
 
 If you only need GNU make for parts of the package which are rarely
 needed (for example to create bibliography files under
@@ -6148,14 +6155,18 @@
 @item
 In C++ code
 @example
-using namesapace std; 
+using namespace std; 
 @end example
 @noindent
 is not good practice, and has caused platform-dependent errors if
 included before headers, especially system headers (which may be
 included by other headers). The best practice is to use explicit
 @code{std::} prefixes for all functions declared by the C++ standard to
-be in that namespace.
+be in that namespace.  It is an error to use @code{using namespace
+std} before including any C++ headers, and some recent compilers will
+warn if this is done.
+@c LLVM and Apple clang and Intel icpx do.
+
 
 @item
 @c including @I{LLVM} clang as from 4.0.0
@@ -6312,6 +6323,15 @@
 use C code (which can normally be mixed with C++ code in a package).
 
 @item
+Include only what is essential in @code{extern "C" @{@}} blocks in C++
+code.  In particular it is not portable to include @R{} headers in such
+blocks (although they are themselves C code, they may include C++ system
+headers and the public ones already enclose their declarations in such a
+block).  And maintainers have include @R{} headers from other headers
+included in such a block.
+@c obscure compilation failures seen with clang++/libc++
+
+@item
 @code{reinterpret_cast} in C++ is not safe for pointers: for example the types
 may have different alignment requirements.  Use @code{memcpy} to copy
 the contents to a fresh variable of the destination type.
@@ -6359,20 +6379,21 @@
 Be careful if using @code{malloc} or @code{calloc}.  First, their return
 value must always be checked to see if the allocation succeeded -- it is
 almost always easier to use @R{}'s @code{R_Calloc}, which does check.
-Second, the first argument is of type @code{size_t} and recent compilers
-are warning about passing signed arguments (which could get promoted to
-ridiculously large values).
+Second, the first argument is of type @code{size_t}@footnote{an unsigned
+64-bit integer type on recent @R{} platforms.} and some recent compilers
+warn about passing @code{int} (signed) arguments (which could get
+promoted to ridiculously large values).
 
 @item
 For C code, consider using the flag @option{-Wstrict-prototypes} which
-is supported by @command{gcc} and @I{LLVM} and Apple @command{clang}.  This
-has found quite a number of errors where functions have been declared
-without arguments and is likely to become the default in future
-compilers.  (It already is for @I{LLVM} @command{clang} in C23 mode.)  Note
-that using @code{f()} for a function without any parameters was
-deprecated in C99 and C11, but it expected to be non-deprecated in C23.
-However, @code{f(void)} is supported by all standards and avoids any
-uncertainty.
+is supported by @command{gcc} and @I{LLVM} and Apple @command{clang}.
+This has found quite a number of errors where functions have been
+declared without arguments and is likely to become the default in future
+compilers.  (It already is for Apple @command{clang} and for @I{LLVM}
+@command{clang} in C23 mode.)  Note that using @code{f()} for a function
+without any parameters was deprecated in C99 and C11, but it expected to
+be non-deprecated in C23.  However, @code{f(void)} is supported by all
+standards and avoids any uncertainty.
 @c draft n3054 §6.7.6.3 point 13 and footnote.
 
 @I{LLVM} @command{clang} has a separate warning
@@ -12721,7 +12742,7 @@
 
 What happens if the @code{SEXP} is not of the correct type?  Sometimes
 you have no other option except to generate an error.  You can use the
-function @code{error} for this.  It is usually better to coerce the
+function @code{Rf_error} for this.  It is usually better to coerce the
 object to the correct type.  For example, if you find that an
 @code{SEXP} is of the type @code{INTEGER}, but you need a @code{REAL}
 object, you can change the type by using
@@ -14543,7 +14564,9 @@
 should be regarded as undocumented and unstable.
 
 Most of these header files, including all those included by @file{R.h},
-can be used from C++ code.
+can be used from C++ code.  (However, they cannot safely be included in
+a @code{extern "C" @{ @}} block as they may include C++ headers when
+included from C++ code---and whether this succeeds is system-specific).
 
 @quotation Note
 Because @R{} re-maps many of its external names to avoid clashes with
@@ -14789,8 +14812,9 @@
 giving the error message. (Don't do this if the string contains @samp{%}
 or might otherwise be interpreted as a format.)
 
-These are defined in header @file{R_ext/Error.h} included by
-@file{R.h}.
+These are defined in header @file{R_ext/Error.h} included by @file{R.h}.
+@strong{NB}: when @code{R_NO_REMAP} is defined (as is recommeneded for
+C++ code), @code{Rf_error} etc must be used.
 
 @menu
 * Error signaling from Fortran::
@@ -14800,8 +14824,8 @@
 @subsection Error signaling from Fortran
 @cindex Error signaling from Fortran
 
-There are two interface function provided to call @code{error} and
-@code{warning} from Fortran code, in each case with a simple character
+There are two interface function provided to call @code{Rf_error} and
+@code{Rf_warning} from Fortran code, in each case with a simple character
 string argument.  They are defined as
 
 @example
@@ -14920,7 +14944,7 @@
           subroutine putRNGseed() bind(C, name = "PutRNGstate")
           end subroutine putRNGseed
         end interface
-      end module
+      end module rngfuncs
       
       subroutine testit
       use rngfuncs
@@ -14929,7 +14953,7 @@
       X = unifRand()
       print *, X
       call putRNGSeed()
-      end
+      end subroutine testit
 @end example
 
 
@@ -15085,10 +15109,11 @@
 to declare a Fortran routine in C before use
 @item F77_CALL(@var{name})
 to call a Fortran routine from C
-@item F77_COMDECL(@var{name})
-to declare a Fortran common block in C
-@item F77_COM(@var{name})
-to access a Fortran common block from C
+@c Never used in R nor current packages
+@c @item F77_COMDECL(@var{name})
+@c to declare a Fortran common block in C
+@c @item F77_COM(@var{name})
+@c to access a Fortran common block from C
 @end table
 
 On most current platforms these are all the same, but it is unwise to
@@ -15748,15 +15773,15 @@
 @end deftypefun
 
 @deftypefun double fprec (double @var{x}, double @var{digits})
-Returns the value of @var{x} rounded to @var{digits} decimal digits
-(after the decimal point).
+Returns the value of @var{x} rounded to @var{digits} @emph{significant}
+decimal digits.
 
 This is the function used by @R{}'s @code{signif()}.
 @end deftypefun
 
 @deftypefun double fround (double @var{x}, double @var{digits})
-Returns the value of @var{x} rounded to @var{digits} @emph{significant}
-decimal digits.
+Returns the value of @var{x} rounded to @var{digits} decimal digits
+(after the decimal point).
 
 This is the function used by @R{}'s @code{round()}.  (Note that C99/C++11
 provide a @code{round} function but C++98 need not.)
@@ -15811,11 +15836,11 @@
 @end multitable
 @end quotation
 
-There are a set of constants (@code{PI}, @code{DOUBLE_EPS}) (and so on)
-defined (unless @code{STRICT_R_HEADERS} is defined) in the included
-header @file{R_ext/Constants.h}, mainly for compatibility with @Sl{}.
-All but @code{PI} are deprecated and should be replaced by the C99/C++11
-versions used in that file.
+For compatibility with @Sl{} this file defines the constant @code{PI}
+(unless @code{STRICT_R_HEADERS} is defined): this is deprecated and
+should be replaced by @code{M_PI}. @file{Constants.h} includes either C
+header @file{float.h} or C++ header @file{cfloat}, which provide
+constants such as @code{DBL_MAX}.
 
 @findex TRUE
 @findex FALSE
@@ -16235,7 +16260,7 @@
 mechanism so are subject to some overhead.
 
 @code{R_withCallingErrorHandler} establishes a calling handler for
-conditions inheriting form class @code{error}.  It establishes the
+conditions inheriting from class @code{error}.  It establishes the
 handler without calling back into @R{} and will therefore be more
 efficient.
 
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/doc/manual/rw-FAQ.texi R-patched/doc/manual/rw-FAQ.texi
--- R-release-orig/doc/manual/rw-FAQ.texi	2024-04-06 00:15:01.000000000 +0200
+++ R-patched/doc/manual/rw-FAQ.texi	2024-10-14 17:45:06.236639361 +0200
@@ -2011,7 +2011,7 @@
 If you want output to be updated on the console, call
 @code{R_FlushConsole()} and then @code{R_ProcessEvents()}.
 
-@set LASTEDIT 2022-04-12
+@set LASTEDIT 2024-04-05
 @ifhtml
 @html
 <hr>
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/extra/tzone/Make.zi R-patched/src/extra/tzone/Make.zi
--- R-release-orig/src/extra/tzone/Make.zi	2024-02-02 00:15:01.000000000 +0100
+++ R-patched/src/extra/tzone/Make.zi	2024-09-12 17:45:06.604964038 +0200
@@ -1,6 +1,6 @@
 ## Makefile to be run on a Unix box with zic
 
-VERSION = 2024a
+VERSION = 2024b
 TZDIR = zoneinfo
 TZTMP = tz
 TARFILE = tzdata$(VERSION).tar.gz
Binary files R-release-orig/src/extra/tzone/zoneinfo.zip and R-patched/src/extra/tzone/zoneinfo.zip differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/gnuwin32/system.c R-patched/src/gnuwin32/system.c
--- R-release-orig/src/gnuwin32/system.c	2024-03-27 00:02:03.000000000 +0100
+++ R-patched/src/gnuwin32/system.c	2024-10-11 01:31:06.000000000 +0200
@@ -434,8 +434,12 @@
 	err = (res == (size_t)(-1));
 	/* errors lead to part of the input line being ignored */
 	if(err) {
+	    /* Should re-set with a stateful encoding, but some iconv
+	       implementations forget byte-order learned from BOM. 
+
 	    Riconv(cd, NULL, NULL, &ob, &onb);
 	    *ob = '\0';
+	    */
 	    printf(_("<ERROR: re-encoding failure from encoding '%s'>\n"),
 		       R_StdinEnc);
 	}
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/include/R_ext/RS.h R-patched/src/include/R_ext/RS.h
--- R-release-orig/src/include/R_ext/RS.h	2023-05-02 00:15:02.000000000 +0200
+++ R-patched/src/include/R_ext/RS.h	2024-09-12 17:45:06.757027961 +0200
@@ -1,6 +1,6 @@
 /*
  *  R : A Computer Language for Statistical Data Analysis
- *  Copyright (C) 1999-2022 The R Core Team.
+ *  Copyright (C) 1999-2024 The R Core Team.
  *
  *  This header file is free software; you can redistribute it and/or modify
  *  it under the terms of the GNU Lesser General Public License as published by
@@ -36,7 +36,7 @@
 # define R_SIZE_T size_t
 #endif
 
-#include <Rconfig.h>		/* for F77_APPEND_UNDERSCORE */
+#include <Rconfig.h>		/* for HAVE_F77_UNDERSCORE */
 
 #ifdef  __cplusplus
 extern "C" {
@@ -71,7 +71,34 @@
 
 /* S Like Fortran Interface */
 /* These may not be adequate everywhere. Convex had _ prepending common
-   blocks, and some compilers may need to specify Fortran linkage */
+   blocks, and some compilers may need to specify Fortran linkage.
+
+   HP-UX did not add a trailing underscore.  (It still existed in
+   2024, but R poiorts had not been seen for many years.)
+
+   Note that this is an F77 interface, intended only for valid F77
+   names of <= 6 ASCII characters (and no underscores) and there is an
+   implicit assumption that the Fortran compiler maps names to
+   lower-case (and 'x' is lower-case when called).
+
+   The configure code has
+
+   HAVE_F77_EXTRA_UNDERSCORE
+   Define if your Fortran compiler appends an extra_underscore to
+   external names containing an underscore.
+
+   but that is not used here (and none of gfortran, flang-new nor
+   x86_64 ifx do so: earlier Intel x86 compilere might have).  It is
+   used in Rdynload.c to support .Fortran.
+
+   These macros have always been the same in R.  Their documented uses are
+
+   F77_SUB to define a function in C to be called from Fortran 
+   F77_NAME to declare a Fortran routine in C before use 
+   F77_CALL to call a Fortran routine from C
+
+   F77_SYMNOL in Defn.h is the same as F77_SUB.
+ */
 
 #ifdef HAVE_F77_UNDERSCORE
 # define F77_CALL(x)	x ## _
@@ -80,6 +107,7 @@
 #endif
 #define F77_NAME(x)    F77_CALL(x)
 #define F77_SUB(x)     F77_CALL(x)
+/* Last two are historical from S, not used in R, deprecated and  not longer documented */
 #define F77_COM(x)     F77_CALL(x)
 #define F77_COMDECL(x) F77_CALL(x)
 
Binary files R-release-orig/src/library/Recommended/MASS.tgz and R-patched/src/library/Recommended/MASS.tgz differ
Only in R-release-orig/src/library/Recommended: MASS_7.3-60.2.tar.gz
Binary files R-release-orig/src/library/Recommended/MASS_7.3-61.tar.gz and R-patched/src/library/Recommended/MASS_7.3-61.tar.gz differ
Binary files R-release-orig/src/library/Recommended/boot.tgz and R-patched/src/library/Recommended/boot.tgz differ
Only in R-release-orig/src/library/Recommended: boot_1.3-30.tar.gz
Binary files R-release-orig/src/library/Recommended/boot_1.3-31.tar.gz and R-patched/src/library/Recommended/boot_1.3-31.tar.gz differ
Binary files R-release-orig/src/library/Recommended/foreign.tgz and R-patched/src/library/Recommended/foreign.tgz differ
Only in R-release-orig/src/library/Recommended: foreign_0.8-86.tar.gz
Binary files R-release-orig/src/library/Recommended/foreign_0.8-87.tar.gz and R-patched/src/library/Recommended/foreign_0.8-87.tar.gz differ
Binary files R-release-orig/src/library/Recommended/nlme.tgz and R-patched/src/library/Recommended/nlme.tgz differ
Only in R-release-orig/src/library/Recommended: nlme_3.1-164.tar.gz
Binary files R-release-orig/src/library/Recommended/nlme_3.1-166.tar.gz and R-patched/src/library/Recommended/nlme_3.1-166.tar.gz differ
Binary files R-release-orig/src/library/Recommended/survival.tgz and R-patched/src/library/Recommended/survival.tgz differ
Only in R-release-orig/src/library/Recommended: survival_3.6-4.tar.gz
Binary files R-release-orig/src/library/Recommended/survival_3.7-0.tar.gz and R-patched/src/library/Recommended/survival_3.7-0.tar.gz differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/base/man/debug.Rd R-patched/src/library/base/man/debug.Rd
--- R-release-orig/src/library/base/man/debug.Rd	2020-06-24 00:15:08.000000000 +0200
+++ R-patched/src/library/base/man/debug.Rd	2024-07-16 11:39:22.000000000 +0200
@@ -108,7 +108,7 @@
 \dontrun{
 debugonce(sample)
 ## only the first call will be debugged
-sampe(10, 1)
+sample(10, 1)
 sample(10, 1)
 }
 }
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/base/man/drop.Rd R-patched/src/library/base/man/drop.Rd
--- R-release-orig/src/library/base/man/drop.Rd	2024-03-27 00:02:04.000000000 +0100
+++ R-patched/src/library/base/man/drop.Rd	2024-08-05 17:45:08.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/base/man/drop.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 1995-2021 R Core Team
+% Copyright 1995-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{drop}
@@ -21,8 +21,10 @@
   \code{x}, but with any extents of length one removed.  Any
   accompanying \code{dimnames} attribute is adjusted and returned with
   \code{x}: if the result is a vector the \code{names} are taken from
-  the \code{dimnames} (if any).  If the result is a length-one vector,
-  the names are taken from the first dimension with a \I{dimname}.
+  the \code{dimnames} (if any).  However, if the result is a vector
+  of length one, then it does not get \code{names} \emph{unless} exactly
+  one component of the \code{dimnames} is non-\code{NULL}, in which case
+  that component is used.
 
   Array subsetting (\code{\link{[}}) performs this reduction unless used
   with \code{drop = FALSE}, but sometimes it is useful to invoke
@@ -34,6 +36,13 @@
 }
 \examples{
 dim(drop(array(1:12, dim = c(1,3,1,1,2,1,2)))) # = 3 2 2
-drop(1:3 \%*\% 2:4)  # scalar product
+drop(1:3 \%*\% 2:4)  # scalar product - w/o drop(.), would return 1x1 matrix
+
+# Behavior when result is length-1 vector:
+(x <- x1 <- x2 <- array(0, c(1L, 1L), list("a", "b")))
+colnames(x1) <- rownames(x2) <- NULL
+names(drop(x )) # NULL
+names(drop(x1)) #  "a"
+names(drop(x2)) #  "b"
 }
 \keyword{array}
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/base/man/is.recursive.Rd R-patched/src/library/base/man/is.recursive.Rd
--- R-release-orig/src/library/base/man/is.recursive.Rd	2024-03-27 00:02:04.000000000 +0100
+++ R-patched/src/library/base/man/is.recursive.Rd	2024-07-16 11:39:22.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/base/man/is.recursive.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 1995-2023 R Core Team
+% Copyright 1995-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{is.recursive}
@@ -14,6 +14,7 @@
 \description{
   \code{is.atomic} returns \code{TRUE} if \code{x} is of an atomic type
   and \code{FALSE} otherwise.
+  \code{is.atomic(NULL)} returns \code{FALSE} since \R version 4.4.0.
 
   \code{is.recursive} returns \code{TRUE} if \code{x} has a recursive
   (list-like) structure and \code{FALSE} otherwise.
@@ -60,6 +61,10 @@
 is.a.r(expression(x+1)) # FALSE TRUE
 is.a.r(quote(exp))      # FALSE FALSE
 is.a.r(NULL)            # FALSE FALSE
+
+# Reproduce pre-4.4 behavior of is.atomic()
+is.atomicN <- function(x) is.atomic(x) || is.null(x)
+is.atomicN(NULL) # TRUE
 }
 \keyword{programming}
 \keyword{classes}
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/base/man/ns-reflect.Rd R-patched/src/library/base/man/ns-reflect.Rd
--- R-release-orig/src/library/base/man/ns-reflect.Rd	2021-01-04 00:15:01.000000000 +0100
+++ R-patched/src/library/base/man/ns-reflect.Rd	2024-10-18 17:45:06.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/base/man/ns-reflect.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 2003-2020 R Core Team
+% Copyright 2003-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{ns-reflect}
@@ -48,10 +48,16 @@
   and subject to change.
 
   \code{getNamespaceName} and \code{getNamespaceVersion} return the name
-  and version of the namespace \code{ns}.
+  and version of the namespace \code{ns} as character strings.
 
   \code{getNamespaceUsers} returns a character vector of the names of
   the namespaces that import namespace \code{ns}.
 }
+\note{
+  Comparison of versions should use \code{\link{compareVersion}} or
+\preformatted{
+    as.package_version(getNamespaceVersion(ns))
+}
+}
 \keyword{internal}
 \author{Luke Tierney}
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/base/man/print.default.Rd R-patched/src/library/base/man/print.default.Rd
--- R-release-orig/src/library/base/man/print.default.Rd	2024-06-01 00:15:01.000000000 +0200
+++ R-patched/src/library/base/man/print.default.Rd	2024-07-16 11:39:23.000000000 +0200
@@ -51,7 +51,8 @@
 \details{
   The default for printing \code{NA}s is to print \code{NA} (without
   quotes) unless this is a character \code{NA} \emph{and} \code{quote =
-    FALSE}, when \samp{<NA>} is printed.
+    FALSE}, when \samp{<NA>} is printed.  When \code{na.print} is not \code{NULL},
+  it handles how character \code{NA} is displayed, with no interaction with \code{quote}.
 
   The same number of decimal places is used throughout a vector.  This
   means that \code{digits} specifies the minimum number of significant
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/grDevices/src/devQuartz.c R-patched/src/library/grDevices/src/devQuartz.c
--- R-release-orig/src/library/grDevices/src/devQuartz.c	2023-11-01 00:15:01.000000000 +0100
+++ R-patched/src/library/grDevices/src/devQuartz.c	2024-07-24 07:45:08.000000000 +0200
@@ -1939,10 +1939,16 @@
 static double RQuartz_StrWidth(const char *text, CTXDESC)
 {
     DEVSPEC;
-    if (!ctx) NOCTXR(strlen(text) * 10.0); /* for sanity reasons */
-    RQuartz_SetFont(ctx, gc, xd);
 
-    CGFontRef font = CGContextGetFont(ctx);
+    CGFontRef font = 0;
+    if (!ctx) { /* if there is no context then don't set the font */
+        xd->async = 1; /* flag us as not having a context */
+        font = RQuartz_Font(gc, NULL);
+        if (!font) return (strlen(text) * 10.0); /* for sanity reasons */
+    } else {
+        RQuartz_SetFont(ctx, gc, xd);
+        font = CGContextGetFont(ctx);
+    }
     float aScale   = (float)((gc->cex * gc->ps * xd->tscale) /
 			     CGFontGetUnitsPerEm(font));
     UniChar *buffer;
@@ -2547,15 +2553,24 @@
 		   pDevDesc dd)
 {
     DRAWSPEC;
-    if (!ctx) { /* dummy data if we have no context, for sanity reasons */
-        *ascent = 10.0;
-        *descent= 2.0;
-        *width  = 9.0;
-        NOCTX;
+    CGFontRef font = 0;
+
+    if (!ctx) {
+        xd->async = 1; /* flag us as not having a context */
+        font = RQuartz_Font(gc, NULL);
+        if (!font) {
+            /* dummy data if we have no font at all, for sanity reasons */
+            *ascent = 10.0;
+            *descent= 2.0;
+            *width  = 9.0;
+            return;
+        }
+    } else {
+        RQuartz_SetFont(ctx, gc, xd);
+        font = CGContextGetFont(ctx);
     }
-    RQuartz_SetFont(ctx, gc, xd);
+
     {
-	CGFontRef font = CGContextGetFont(ctx);
         float aScale   = (float)((gc->cex * gc->ps * xd->tscale) /
 				 CGFontGetUnitsPerEm(font));
 	UniChar  *buffer, single;
@@ -3002,14 +3017,12 @@
 
     Rboolean grouping = QuartzBegin(&ctx, &layer, xd);
 
-    char url[501];
-    snprintf(url, 500, "file://%s", R_GE_glyphFontFile(font));
-    CFStringRef cfFontFileName = 
-        CFStringCreateWithCString(NULL, url, kCFStringEncodingUTF8);
-    CFURLRef cfFontURL = CFURLCreateWithString(NULL, cfFontFileName, NULL);
+    const char* path = R_GE_glyphFontFile(font);
+    CFURLRef cfFontURL = CFURLCreateFromFileSystemRepresentation(NULL, (const UInt8*)path, strlen(path), false);
+    if (!cfFontURL)
+        error(_("Invalid font path: \"%s\""), path);
     CFArrayRef cfFontDescriptors = 
         CTFontManagerCreateFontDescriptorsFromURL(cfFontURL);
-    CFRelease(cfFontFileName);
     CFRelease(cfFontURL);
     int n_fonts = CFArrayGetCount(cfFontDescriptors);
     if (n_fonts > 0) {
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/grDevices/src/devices.c R-patched/src/library/grDevices/src/devices.c
--- R-release-orig/src/library/grDevices/src/devices.c	2023-03-24 00:02:03.000000000 +0100
+++ R-patched/src/library/grDevices/src/devices.c	2024-07-24 07:45:08.000000000 +0200
@@ -226,7 +226,7 @@
     UNPROTECT(1);
 
     /* Further capabilities can be filled in by device */
-    if (dd->deviceVersion >= R_GE_group) {
+    if (dd->deviceVersion >= R_GE_group && dd->capabilities) {
         devcap = dd->capabilities(capabilities);
     } else {
         devcap = capabilities;
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/graphics/man/mtext.Rd R-patched/src/library/graphics/man/mtext.Rd
--- R-release-orig/src/library/graphics/man/mtext.Rd	2024-03-27 00:02:05.000000000 +0100
+++ R-patched/src/library/graphics/man/mtext.Rd	2024-08-05 17:45:08.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/graphics/man/mtext.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 1995-2011 R Core Team
+% Copyright 1995-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{mtext}
@@ -35,8 +35,8 @@
     parallel to the axis the default is to centre the string.}
   \item{padj}{adjustment for each string perpendicular to the reading
     direction (which is controlled by \code{adj}).  For strings parallel
-    to the axes, \code{padj = 0} means left or bottom alignment,
-    and \code{padj = 1} means right or top alignment (relative to the line).
+    to the axes, \code{padj = 0} means bottom alignment,
+    and \code{padj = 1} means top alignment (relative to the axis line).
     
     If \code{padj} is not a finite value (the default), the value of
     \code{par("las")} determines the adjustment.  For strings plotted
@@ -103,5 +103,10 @@
 ##--- log axis :
 plot(1:10, exp(1:10), log = "y", main = "log =\"y\"", xlab = "xlab")
 for(s in 1:4) mtext(paste("mtext(...,side=", s ,")"), side = s)
+
+##--- illustrating padj behavior :
+plot(0, axes=FALSE, ann=FALSE, frame.plot=TRUE)
+for(si in 1:4) mtext(c("padj=0", "-----------", "padj=1"),
+                     side = si, padj = c(0, 0.5, 1))
 }
 \keyword{aplot}
Binary files R-release-orig/src/library/grid/inst/doc/displaylist.pdf and R-patched/src/library/grid/inst/doc/displaylist.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/frame.pdf and R-patched/src/library/grid/inst/doc/frame.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/grid.pdf and R-patched/src/library/grid/inst/doc/grid.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/grobs.pdf and R-patched/src/library/grid/inst/doc/grobs.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/interactive.pdf and R-patched/src/library/grid/inst/doc/interactive.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/locndimn.pdf and R-patched/src/library/grid/inst/doc/locndimn.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/moveline.pdf and R-patched/src/library/grid/inst/doc/moveline.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/nonfinite.pdf and R-patched/src/library/grid/inst/doc/nonfinite.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/plotexample.pdf and R-patched/src/library/grid/inst/doc/plotexample.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/rotated.pdf and R-patched/src/library/grid/inst/doc/rotated.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/saveload.pdf and R-patched/src/library/grid/inst/doc/saveload.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/sharing.pdf and R-patched/src/library/grid/inst/doc/sharing.pdf differ
Binary files R-release-orig/src/library/grid/inst/doc/viewports.pdf and R-patched/src/library/grid/inst/doc/viewports.pdf differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/methods/R/RClassUtils.R R-patched/src/library/methods/R/RClassUtils.R
--- R-release-orig/src/library/methods/R/RClassUtils.R	2024-03-27 00:02:05.000000000 +0100
+++ R-patched/src/library/methods/R/RClassUtils.R	2024-10-13 01:31:06.000000000 +0200
@@ -1833,6 +1833,10 @@
     if(!is.null(pkgN <- get0(".packageName", topEnv, inherits=TRUE)) &&
        .identC(package, pkgN))
         return(topEnv) # kludge for source'ing package code
+    ## If called from .findInheritedMethods which disables S4 primitive dispatch,
+    ## allow it here, as namespace loading hooks may need it:
+    if(!.allowPrimitiveMethods(TRUE))
+        on.exit(.allowPrimitiveMethods(FALSE))
     if(nzchar(package) && require(package, character.only = TRUE)) {}
     else {
         if(mustFind)
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/methods/R/methodsTable.R R-patched/src/library/methods/R/methodsTable.R
--- R-release-orig/src/library/methods/R/methodsTable.R	2024-03-27 00:02:05.000000000 +0100
+++ R-patched/src/library/methods/R/methodsTable.R	2024-10-13 01:31:06.000000000 +0200
@@ -464,8 +464,8 @@
              where = environment(fdef))
 {
     ## to avoid infinite recursion, and somewhat for speed, turn off S4 methods for primitives
-    primMethods <- .allowPrimitiveMethods(FALSE)
-    on.exit(.allowPrimitiveMethods(primMethods))
+    if(.allowPrimitiveMethods(FALSE)) # if it was true, revert on exit
+        on.exit(.allowPrimitiveMethods(TRUE))
     ## classes is a list of the class(x) for each arg in generic
     ## signature, with "missing" for missing args
     if(!is.environment(table)) {
Binary files R-release-orig/src/library/parallel/inst/doc/parallel.pdf and R-patched/src/library/parallel/inst/doc/parallel.pdf differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/stats/man/kernel.Rd R-patched/src/library/stats/man/kernel.Rd
--- R-release-orig/src/library/stats/man/kernel.Rd	2024-04-03 00:15:01.000000000 +0200
+++ R-patched/src/library/stats/man/kernel.Rd	2024-09-18 17:45:06.000000000 +0200
@@ -38,7 +38,7 @@
     kernels of dimension \code{m[j]}, for \code{j in 1:length(m)}.
     Currently this is supported only for the named \code{"*daniell"} kernels.}
   \item{name}{the name the kernel will be called.}
-  \item{r}{the kernel order for a \I{Fejer} kernel.}
+  \item{r}{the kernel order for a \I{Dirichlet} or \I{Fejer} kernel.}
   \item{k, x}{a \code{"tskernel"} object.}
   \item{type, xlab, ylab, main, \dots}{arguments passed to
     \code{\link{plot.default}}.}
@@ -103,4 +103,3 @@
 spectrum(sunspot.year, kernel = kernel("daniell", c(11,7,3)), log = "no")
 }
 \keyword{ts}
-
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/tools/R/utils.R R-patched/src/library/tools/R/utils.R
--- R-release-orig/src/library/tools/R/utils.R	2024-06-01 00:15:01.000000000 +0200
+++ R-patched/src/library/tools/R/utils.R	2024-07-16 11:40:42.000000000 +0200
@@ -1909,6 +1909,8 @@
                          "dim.rename.nc", "open.nc", "print.nc"),
              Rmpfr = c("mpfr.is.0", "mpfr.is.integer"),
              SMPracticals = "exp.gibbs",
+             SparseM = c("as.matrix.csc","as.matrix.csr", "as.matrix.ssc", "as.matrix.ssr", "as.matrix.coo",
+                         "is.matrix.csc","is.matrix.csr", "is.matrix.ssc", "is.matrix.ssr", "is.matrix.coo"),
              TANOVA = "sigma.hat",
              TeachingDemos = "sigma.test",
              XML = "text.SAX",
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/R/packages.R R-patched/src/library/utils/R/packages.R
--- R-release-orig/src/library/utils/R/packages.R	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/library/utils/R/packages.R	2024-09-29 01:31:05.000000000 +0200
@@ -1202,7 +1202,7 @@
 }
 
 ## default is included in setRepositories.Rd (via \Sexpr)
-.BioC_version_associated_with_R_version_default <- "3.19"
+.BioC_version_associated_with_R_version_default <- "3.20"
 .BioC_version_associated_with_R_version <- function ()
     numeric_version(Sys.getenv("R_BIOC_VERSION",
                                .BioC_version_associated_with_R_version_default))
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/R/sessionInfo.R R-patched/src/library/utils/R/sessionInfo.R
--- R-release-orig/src/library/utils/R/sessionInfo.R	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/library/utils/R/sessionInfo.R	2024-09-17 17:45:11.000000000 +0200
@@ -72,13 +72,14 @@
                                       "16" = "Big Sur ...",
                                       ""),
                                ver)
-                   else if(ver1[1L] <= "14")
+                   else if(ver1[1L] <= "15")
                         sprintf("macOS %s %s",
                                switch(ver1[1L],
                                       "11" = "Big Sur",
                                       "12" = "Monterey",
                                       "13" = "Ventura",
-                                      "14" = "Sonoma"),
+                                      "14" = "Sonoma",
+                                      "15" = "Sequoia"),
                                ver)
                    else
                        sprintf("macOS %s", ver)
Binary files R-release-orig/src/library/utils/inst/doc/Sweave.pdf and R-patched/src/library/utils/inst/doc/Sweave.pdf differ
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/man/compareVersion.Rd R-patched/src/library/utils/man/compareVersion.Rd
--- R-release-orig/src/library/utils/man/compareVersion.Rd	2018-09-25 10:45:44.000000000 +0200
+++ R-patched/src/library/utils/man/compareVersion.Rd	2024-10-18 17:45:07.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/utils/man/compareVersion.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 1995-2007 R Core Team
+% Copyright 1995-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{compareVersion}
@@ -19,6 +19,8 @@
   \code{0} if the numbers are equal, \code{-1} if \code{b} is later
   and \code{1} if \code{a} is later (analogous to the C function
   \code{strcmp}).
+
+  Gives an \R error on malformed inputs.
 }
 \details{
   \R package version numbers are of the form \code{x.y-z} for integers
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/man/person.Rd R-patched/src/library/utils/man/person.Rd
--- R-release-orig/src/library/utils/man/person.Rd	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/library/utils/man/person.Rd	2024-09-10 17:45:06.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/utils/man/person.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 1995-2020 R Core Team
+% Copyright 1995-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{person}
@@ -137,7 +137,9 @@
       substantial contributions to the package.}
     \item{\code{"cph"}}{(Copyright holder) Use for all copyright
       holders.  This is a legal concept so should use the legal name of
-      an institution or corporate body.}
+      an institution or corporate body.  Note that authors which are
+      \sQuote{natural persons} are by default copyright holders and so
+      do not need to be given this role.}
     \item{\code{"cre"}}{(Creator) Use for the package maintainer.}
     \item{\code{"ctb"}}{(Contributor) Use for authors who have made
       smaller contributions (such as code patches etc.) but should not
@@ -169,7 +171,10 @@
   information), and be displayed as the corresponding \abbr{URI}s by the
   \code{print()} and \code{format()} methods (see \bold{Examples}
   below).
-  
+
+  Where more than one entity is given a \code{"cph"} role, the
+  \code{comment} field should be used to delimit who owns the copyright
+  to what parts of the package.
 }
 \seealso{
   \code{\link{citation}}
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/man/tar.Rd R-patched/src/library/utils/man/tar.Rd
--- R-release-orig/src/library/utils/man/tar.Rd	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/library/utils/man/tar.Rd	2024-09-17 17:45:11.000000000 +0200
@@ -1,6 +1,6 @@
 % File src/library/utils/man/tar.Rd
 % Part of the R package, https://www.R-project.org
-% Copyright 2009-2023 R Core Team
+% Copyright 2009-2024 R Core Team
 % Distributed under GPL 2 or later
 
 \name{tar}
@@ -54,8 +54,9 @@
   \samp{--acls}, \option{--exclude-backups}, \option{--exclude-vcs} (and
   similar) and on Windows \option{--force-local} (so drives can be
   included in filepaths). \command{Rtools} 4 and earlier included a
-  \command{tar} which used \option{--force-local}, but \command{Rtools} 4.2
-  includes original GNU \command{tar}, which does not use it by default.
+  \command{tar} which used \option{--force-local}, but \command{Rtools}
+  >= 4.2 include the original GNU \command{tar}, which does not use it
+  by default.
 
   A convenient and robust way to set options for GNU \command{tar} is via
   environment variable \env{TAR_OPTIONS}.  Appending \option{--force-local}
@@ -68,11 +69,13 @@
   For GNU \command{tar},
   \option{--format=ustar} forces a more portable format. (The default is
   set at compilation and will be shown at the end of the output from
-  \command{tar --help}: for version 1.30 \sQuote{out-of-the-box} it is 
+  \command{tar --help}: for version 1.34 \sQuote{out-of-the-box} it is 
   \option{--format=gnu}, but the manual says the intention is to change
+  @c https://www.gnu.org/software/tar/manual/tar.html#Formats
   to \option{--format=posix} which is the same as \code{pax} --
   it was never part of the POSIX standard for \command{tar} and should
-  not be used.)
+  not be used.  However, the intention has been stated now for several
+  years without changing the default.)
   For \I{libarchive}'s \command{bsdtar}, \option{--format=ustar} is more
   portable than the default.
   
@@ -104,10 +107,11 @@
   FreeBSD and Windows 10 use \command{bsdtar} from the \I{libarchive}
   project (but for macOS often a quite-old version), and commercial
   Unixes will have their own versions. \command{bsdtar} is available for
-  many other platforms: macOS up to at least 10.9 had GNU \command{tar}
-  as \command{gnutar} and other platforms, e.g.\sspace{}Solaris, have it
-  as \command{gtar}: on a Unix-alike \command{configure} will try
-  \command{gnutar} and \command{gtar} before \code{tar}.
+  many other platforms: macOS up to at least 10.9 (but not recently) had
+  GNU \command{tar} as \command{gnutar} and other platforms,
+  e.g.\sspace{}Solaris, have it as \command{gtar}: on a Unix-alike
+  \command{configure} will try \command{gnutar} and \command{gtar}
+  before \code{tar}.
 
   %% Heirloom Toolchest (http://heirloom.sourceforge.net/) is
   %% another implementation available on NetBSD, but probably not the default.
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/library/utils/src/windows/util.c R-patched/src/library/utils/src/windows/util.c
--- R-release-orig/src/library/utils/src/windows/util.c	2023-03-24 00:02:05.000000000 +0100
+++ R-patched/src/library/utils/src/windows/util.c	2024-07-16 11:41:35.000000000 +0200
@@ -1,7 +1,7 @@
 /*
  *  R : A Computer Language for Statistical Data Analysis
  *  file util.c
- *  Copyright (C) 2005--2023  The R Core Team
+ *  Copyright (C) 2005--2024  The R Core Team
  *  Copyright (C) 1998--2003  Guido Masarotto and Brian Ripley
  *  Copyright (C) 2004	      The R Foundation
  *
@@ -292,15 +292,17 @@
 
     n = length(text);
     if(n > 0) {
-	int len = 1;
+	int len = 0;
 	if(raw) len = n;
-	else if (format == CF_UNICODETEXT)
+	else if (format == CF_UNICODETEXT) {
+	    len = 2; /* terminator */
 	    for(i = 0; i < n; i++)
 		len += 2 * (wcslen(wtransChar(STRING_ELT(text, i))) + 2);
-	else if (format == CF_TEXT || format == CF_OEMTEXT || format == CF_DIF)
+	} else if (format == CF_TEXT || format == CF_OEMTEXT || format == CF_DIF) {
+	    len = 1; /* terminator */
 	    for(i = 0; i < n; i++)
 		len += strlen(translateChar(STRING_ELT(text, i))) + 2;
-	else
+	} else
 	    error("'raw = FALSE' and format is a not a known text format");
 
 	if ( (hglb = GlobalAlloc(GHND, len)) &&
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/main/eval.c R-patched/src/main/eval.c
--- R-release-orig/src/main/eval.c	2024-04-10 00:02:01.000000000 +0200
+++ R-patched/src/main/eval.c	2024-10-02 17:45:13.419254222 +0200
@@ -7485,11 +7485,11 @@
     POP_PENDING_PROMISE(BCFRAME_PRSTACK());
     SEXP prom = BCFRAME_PROMISE();
     R_bcstack_t ubval = POP_BCFRAME(FALSE);
+    BCNPUSH_STACKVAL(ubval); /* push early to protect */
     SET_PROMISE_VALUE_FROM_STACKVAL(prom, ubval);
     SET_PRSEEN(prom, 0);
     SET_PRENV(prom, R_NilValue);
     UNPROTECT(1); /* prom */
-    BCNPUSH_STACKVAL(ubval);
 }
 
 #define DO_GETVAR_FORCE_PROMISE_RETURN() do {			\
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/main/print.c R-patched/src/main/print.c
--- R-release-orig/src/main/print.c	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/main/print.c	2024-09-10 17:45:06.832755841 +0200
@@ -1127,10 +1127,10 @@
 
 attribute_hidden
 #ifdef FC_LEN_T
-void F77_NAME(dblep0) (const char *label, int *nchar, double *data, int *ndata,
+void F77_SUB(dblep0) (const char *label, int *nchar, double *data, int *ndata,
 		       const FC_LEN_T label_len)
 #else
-void F77_NAME(dblep0) (const char *label, int *nchar, double *data, int *ndata)
+void F77_SUB(dblep0) (const char *label, int *nchar, double *data, int *ndata)
 #endif
 {
     int nc = *nchar;
@@ -1147,10 +1147,10 @@
 
 attribute_hidden
 #ifdef FC_LEN_T
-void F77_NAME(intpr0) (const char *label, int *nchar, int *data, int *ndata,
+void F77_SUB(intpr0) (const char *label, int *nchar, int *data, int *ndata,
 		       const FC_LEN_T label_len)
 #else
-void F77_NAME(intpr0) (const char *label, int *nchar, int *data, int *ndata)
+void F77_SUB(intpr0) (const char *label, int *nchar, int *data, int *ndata)
 #endif
 {
     int nc = *nchar;
@@ -1168,10 +1168,10 @@
 
 attribute_hidden
 #ifdef FC_LEN_T
-void F77_NAME(realp0) (const char *label, int *nchar, float *data, int *ndata,
+void F77_SUB(realp0) (const char *label, int *nchar, float *data, int *ndata,
 		      const FC_LEN_T label_len)
 #else
-void F77_NAME(realp0) (const char *label, int *nchar, float *data, int *ndata)
+void F77_SUB(realp0) (const char *label, int *nchar, float *data, int *ndata)
 #endif
 {
     int nc = *nchar, nd = *ndata;
@@ -1198,10 +1198,10 @@
 /* Fortran-callable error routine for lapack */
 
 #ifdef FC_LEN_T
-NORET void F77_NAME(xerbla)(const char *srname, int *info,
+NORET void F77_SUB(xerbla)(const char *srname, int *info,
 			    const FC_LEN_T srname_len)
 #else
-NORET void F77_NAME(xerbla)(const char *srname, int *info)
+NORET void F77_SUB(xerbla)(const char *srname, int *info)
 #endif
 {
    /* srname is not null-terminated.  It will be 6 characters for
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/main/registration.c R-patched/src/main/registration.c
--- R-release-orig/src/main/registration.c	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/main/registration.c	2024-09-10 17:45:06.880278442 +0200
@@ -1,6 +1,6 @@
 /*
  *  R : A Computer Language for Statistical Data Analysis
- *  Copyright (C) 2002-2014	The R Core Team.
+ *  Copyright (C) 2002-2024	The R Core Team.
  *
  *  This program is free software; you can redistribute it and/or modify
  *  it under the terms of the GNU General Public License as published by
@@ -73,7 +73,7 @@
     {NULL, NULL, 0}
 };
 
-
+/* F77_SYMBOL is defined in Defn.h */
 #define FDEF(name, n)  {#name, (DL_FUNC) &F77_SYMBOL(name), n, NULL}
 static R_FortranMethodDef fortranMethods[] = {
     /* LINPACK */
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/main/sysutils.c R-patched/src/main/sysutils.c
--- R-release-orig/src/main/sysutils.c	2024-04-03 00:15:02.000000000 +0200
+++ R-patched/src/main/sysutils.c	2024-10-12 01:31:06.571790934 +0200
@@ -1,6 +1,6 @@
 /*
  *  R : A Computer Language for Statistical Data Analysis
- *  Copyright (C) 1997-2023   The R Core Team
+ *  Copyright (C) 1997-2024   The R Core Team
  *  Copyright (C) 1995-1996   Robert Gentleman and Ross Ihaka
  *
  *  This program is free software; you can redistribute it and/or modify
@@ -791,11 +791,16 @@
 	    } else if(res == -1 && sub &&
 		      (errno == EILSEQ || errno == EINVAL)) {
 		/* it seems this gets thrown for non-convertible input too */
+		/* 
+		   Should re-set with a stateful encoding, but some iconv
+                   implementations forget byte-order learned from BOM.
+
 		res = Riconv(obj, NULL, NULL, &outbuf, &outb);	
 		if (res == -1 && errno == E2BIG) {
 		    R_AllocStringBuffer(2*cbuff.bufsize, &cbuff);
 		    goto top_of_loop;
-		}	
+		}
+		*/
 		if(fromUTF8 && streql(sub, "Unicode")) {
 		    if(outb < 13) {
 			R_AllocStringBuffer(2*cbuff.bufsize, &cbuff);
@@ -921,153 +926,6 @@
     else return CE_NATIVE;
 }
 
-#ifdef __APPLE__
-/* Work-around for libiconv in macOS 14.1. When an invalid input byte is
-   encountered while converting, one has to re-set the converter state.
-   Otherwise, subsequent valid bytes may be reported as invalid and libiconv
-   may crash R due to an assertion failure. The problem does not seem to
-   happen when the converter is re-set after error.
-
-   While often one should reset the converter in such situation in order to
-   support stateful encodings properly, the problem has been seen even when
-   converting from UTF-8 to UTF-8.
-
-   This work-around automatically re-sets the converter in Riconv in case
-   of error for stateless encodings. */
-# define R_MACOS_LIBICONV_WORKAROUND
-
-/* A hack to detect and undo transliteration (experimental, likely to change
-   or be removed).  While POSIX says that iconv should transliterate or
-   substitute valid input characters not representable in the output
-   encoding, this typically is not the case.  Instead, non-representable
-   characters usually cause an error (EILSEQ or even EINVAL) and R ended up
-   depending on that.
-
-   macOS 14.1 has a libiconv implementation which transliterates many
-   characters.
-
-   This feature, currently only available for stateless conversions together
-   with R_MACOS_LIBICONV_WORKAROUND, detects transliteration by converting
-   the result back to the original encoding, compares with the original and
-   then re-rums the conversion only to the to-be-transliterated character. 
-   This wouldn't work in cases when the conversion isn't unique, but such
-   cases are unlikely (note implementations of iconv, including libiconv in
-   macOS 14.1, do not support decomposed forms).
-   
-   Enabled at runtime via _R_ICONV_UNDO_TRANSLITERATION_.
-*/
-
-# define R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-#endif
-
-#ifdef R_MACOS_LIBICONV_WORKAROUND
-typedef struct {
-    iconv_t cd;
-    Rboolean reset_after_error;
-    iconv_t cd_back;
-    Rboolean undo_transliteration;
-    size_t buflen;
-    char *buf;
-} Riconv_cd;
-
-static Rboolean is_stateful(const char *code)
-{
-    /* list from libiconv 1.17, but names are system-specific */
-    static char *stateful[] = {
-        "utf7", "UTF-7", "UNICODE-1-1-UTF-7", "csUnicode11UTF7", "cp1255",
-        "CP1255", "WINDOWS-1255", "MS-HEBR", "cp1258", "CP1258",
-        "WINDOWS-1258", "tcvn", "TCVN", "TCVN-5712", "TCVN5712-1",
-        "TCVN5712-1:1993", "iso2022_jp", "ISO-2022-JP", "csISO2022JP",
-        "iso2022_jp1", "ISO-2022-JP-1", "iso2022_jp2", "ISO-2022-JP-2",
-        "csISO2022JP2", "iso2022_jpms", "ISO-2022-JP-MS", "CP50221",
-        "iso2022_cn", "ISO-2022-CN", "csISO2022CN", "iso2022_cn_ext",
-        "ISO-2022-CN-EXT", "hz", "HZ", "HZ-GB-2312", "big5hkscs1999",
-        "BIG5-HKSCS:1999", "big5hkscs2001", "BIG5-HKSCS:2001",
-        "big5hkscs2004", "BIG5-HKSCS:2004", "big5hkscs2008", "BIG5-HKSCS",
-        "BIG5HKSCS", "BIG5-HKSCS:2008", "iso2022_kr", "ISO-2022-KR",
-        "csISO2022KR", "euc_jisx0213", "EUC-JISX0213", "EUC-JIS-2004",
-        "shift_jisx0213", "SHIFT_JISX0213", "SHIFT_JIS-2004", "iso2022_jp3",
-        "ISO-2022-JP-3", "ISO-2022-JP-2004", NULL
-    };
-
-    if (!strcasecmp(code, "UTF-8") || !strcasecmp(code, "ISO-8859-1") ||
-        !strcasecmp(code, "latin1"))
-	return FALSE;
-
-    /* if performance of this becomes a problem, there could be a cache of
-       recently used encodings or/and a perfect hashing function */
-    for(int i = 0; stateful[i] ; i++)
-	if (!strcasecmp(code, stateful[i]))
-	    return TRUE;
-    return FALSE;
-}
-
-# ifdef R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-static Rboolean is_unicode(const char *code)
-{
-    /* list from libiconv 1.17, but names are system-specific */
-    static char *unicode[] = {
-        "UTF-8",
-        "UCS-4", "UCS-4BE", "UCS-4LE",
-        "UTF-16", "UTF-16BE", "UTF-16LE",
-        "UTF-32", "UTF-32BE", "UTF-32LE",
-        "UTF-7",
-        "C99", "JAVA", NULL
-    };
-
-    for(int i = 0; unicode[i] ; i++)
-	if (!strcasecmp(code, unicode[i]))
-	    return TRUE;
-    return FALSE;
-}
-# endif 
-#endif
-
-static void *iconv_open_internal(const char *tocode, const char *fromcode)
-{
-#ifndef R_MACOS_LIBICONV_WORKAROUND
-    return iconv_open(tocode, fromcode);
-#else
-    iconv_t cd = iconv_open(tocode, fromcode);
-    if (cd == (iconv_t)-1)
-	return cd;
-
-    Riconv_cd *rcd = malloc(sizeof(Riconv_cd));
-    if (!rcd) {
-	errno = ENOMEM;
-	return (void *)(iconv_t)-1;
-    }
-    rcd->cd = cd;
-    rcd->reset_after_error = !(is_stateful(tocode) || is_stateful(fromcode));
-
-    rcd->undo_transliteration = FALSE;
-# ifdef R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-    rcd->undo_transliteration =
-        !is_unicode(tocode) && rcd->reset_after_error;
-	/* (!(is_stateful(tocode) || is_stateful(fromcode))  */
-
-    char *p = getenv("_R_ICONV_UNDO_TRANSLITERATION_");
-    if (!p || !StringTrue(p))
-	rcd->undo_transliteration = FALSE;
-
-    if (rcd->undo_transliteration) {
-	rcd->cd_back = iconv_open(fromcode, tocode);
-	if (rcd->cd_back == (iconv_t)-1) {
-	    iconv_close((iconv_t)rcd->cd);
-	    return (iconv_t)-1;
-	}
-	rcd->buflen = 8192;
-	rcd->buf = malloc(rcd->buflen);
-	if (!rcd->buf) {
-	    iconv_close((iconv_t)rcd->cd);
-	    iconv_close((iconv_t)rcd->cd_back);
-	    return (iconv_t)-1;
-	}
-    }
-# endif
-    return rcd;
-#endif
-}
 
 void * Riconv_open (const char* tocode, const char* fromcode)
 {
@@ -1082,16 +940,16 @@
     if (latin1locale) cp = "ISO-8859-1";
     else if (!utf8locale) cp = locale2charset(NULL);
 # endif
-    if (!*tocode && !*fromcode) return iconv_open_internal(cp, cp);
-    if(!*tocode)  return iconv_open_internal(cp, fromcode);
-    else if(!*fromcode) return iconv_open_internal(tocode, cp);
-    else return iconv_open_internal(tocode, fromcode);
+    if (!*tocode && !*fromcode) return iconv_open(cp, cp);
+    if(!*tocode)  return iconv_open(cp, fromcode);
+    else if(!*fromcode) return iconv_open(tocode, cp);
+    else return iconv_open(tocode, fromcode);
 #else
 // "utf8" is not valid but people keep on using it
     const char *to = tocode, *from = fromcode;
     if(strcasecmp(tocode, "utf8") == 0) to = "UTF-8";
     if(strcasecmp(fromcode, "utf8") == 0) from = "UTF-8";
-    return iconv_open_internal(to, from);
+    return iconv_open(to, from);
 #endif
 }
 
@@ -1104,130 +962,14 @@
 size_t Riconv (void *cd, const char **inbuf, size_t *inbytesleft,
 	       char **outbuf, size_t *outbytesleft)
 {
-#ifdef R_MACOS_LIBICONV_WORKAROUND
-    Riconv_cd *rcd = (Riconv_cd *)cd;
-
-# ifdef R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-    const char *old_inbuf = NULL;
-    size_t old_inbytesleft = 0;
-    char *old_outbuf = NULL;
-    size_t old_outbytesleft = 0;
-
-    if (rcd->undo_transliteration) {
-	old_inbuf = inbuf ? *inbuf : NULL;
-	old_inbytesleft = inbytesleft ? *inbytesleft : 0;
-	old_outbuf = outbuf ? *outbuf : NULL;
-	old_outbytesleft = outbytesleft ? *outbytesleft : 0;
-    }
-# endif
-#endif
-
     /* here libiconv has const char **, glibc has char ** for inbuf */
-    size_t res = iconv(
-#ifdef R_MACOS_LIBICONV_WORKAROUND
-                       rcd->cd,
-#else
-                       (iconv_t)cd,
-#endif
-                       (ICONV_CONST char **) inbuf, inbytesleft,
-                       outbuf, outbytesleft);
-
-#ifdef R_MACOS_LIBICONV_WORKAROUND
-    if (rcd->reset_after_error &&
-	(res == (size_t)-1 && (errno == EILSEQ || errno == EINVAL))) {
-
-	int saveerrno = errno;
-	iconv(rcd->cd, NULL, NULL, NULL, NULL);
-	errno = saveerrno;
-	}
-
-# ifdef R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-    if (rcd->undo_transliteration &&
-        inbuf && inbytesleft && outbuf && outbytesleft) {
-
-	int saveerrno = errno;
-	size_t needed = old_inbytesleft - *inbytesleft;
-	if (rcd->buflen < needed) {
-	    free(rcd->buf);
-	    rcd->buf = malloc(needed);
-	    if (!rcd->buf) {
-		errno = ENOMEM;
-		return -1;
-	    }
-	    rcd->buflen = needed;
-	}
-
-	const char *back_inbuf = old_outbuf;
-	size_t back_inbytesleft = old_outbytesleft - *outbytesleft;
-	char *back_outbuf = rcd->buf;
-	size_t back_outbytesleft = needed;
-
-	iconv(rcd->cd_back, NULL, NULL, NULL, NULL);
-	size_t back_res = iconv(rcd->cd_back,
-	      (ICONV_CONST char **) &back_inbuf,
-	      &back_inbytesleft,
-	      (ICONV_CONST char **) &back_outbuf,
-	      &back_outbytesleft);
-
-	if (back_res == (size_t)-1) {
-	    /* should not happen */
-	    errno = saveerrno;
-	    return res;
-	}
-
-	if (back_outbytesleft == 0 && back_inbytesleft == 0 &&
-	    !memcmp(rcd->buf, old_inbuf, needed)) {
-
-	    /* no transliteration happened */
-	    errno = saveerrno;
-	    return res;
-	}
-
-	size_t stored = needed - back_outbytesleft;
-	size_t i;
-	for(i = 0; i < stored; i++)
-	    if (rcd->buf[i] != old_inbuf[i]) {
-		/* byte at index i in old_inbuf was probably transliterated,
-		   so convert again only i bytes and report error */
-		*inbuf = old_inbuf;
-		*outbuf = old_outbuf;
-		*outbytesleft = old_outbytesleft;
-		size_t reduced = i;
-		res = iconv(rcd->cd,
-		            (ICONV_CONST char **) inbuf,
-		            &reduced,
-		            (ICONV_CONST char **) outbuf,
-		            outbytesleft);
-
-		/* "reduced" should be 0 now */
-		*inbytesleft = old_inbytesleft - (i - reduced);
-		errno = EILSEQ;
-		return -1;
-	    }
-	/* should not be reached */
-	errno = saveerrno;
-    } 
-# endif
-#endif
-    return res;
+    return iconv((iconv_t) cd, (ICONV_CONST char **) inbuf, inbytesleft,
+                outbuf, outbytesleft);
 }
 
 int Riconv_close (void *cd)
 {
-#ifndef R_MACOS_LIBICONV_WORKAROUND
     return iconv_close((iconv_t) cd);
-
-#else
-    Riconv_cd *rcd = (Riconv_cd *)cd;
-    int res = iconv_close(rcd->cd);
-# ifdef R_MACOS_LIBICONV_UNDO_TRANSLITERATION
-    if (rcd->undo_transliteration) {
-	free(rcd->buf);
-	if (iconv_close(rcd->cd_back)) res = -1;
-    }
-# endif
-    return res;
-#endif
 }
 
 typedef enum {
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/main/util.c R-patched/src/main/util.c
--- R-release-orig/src/main/util.c	2024-04-26 00:15:01.000000000 +0200
+++ R-patched/src/main/util.c	2024-09-10 17:45:06.895757239 +0200
@@ -55,6 +55,8 @@
 extern "C" {
 #endif
 
+
+/*  F77_SYMBOL is defined in Defn.h as a minimal F77_SUB. */
 #if defined FC_LEN_T
 # include <stddef.h>
 void F77_SYMBOL(rwarnc)(char *msg, int *nchar, FC_LEN_T msg_len);
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/nmath/d1mach.c R-patched/src/nmath/d1mach.c
--- R-release-orig/src/nmath/d1mach.c	2018-09-25 10:46:56.000000000 +0200
+++ R-patched/src/nmath/d1mach.c	2024-09-10 17:45:07.065041887 +0200
@@ -1,7 +1,7 @@
 /*
  *  Mathlib - A Mathematical Function Library
  *  Copyright (C) 1998  Ross Ihaka
- *  Copyright (C) 2000-2014 The R Core Team
+ *  Copyright (C) 2000-2024 The R Core Team
  *
  *  This program is free software; you can redistribute it and/or modify
  *  it under the terms of the GNU General Public License as published by
@@ -53,7 +53,7 @@
 extern "C" 
 #endif
 
-double F77_NAME(d1mach)(int *i)
+double F77_SUB(d1mach)(int *i)
 {
     return Rf_d1mach(*i);
 }
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/nmath/i1mach.c R-patched/src/nmath/i1mach.c
--- R-release-orig/src/nmath/i1mach.c	2022-03-25 00:02:06.000000000 +0100
+++ R-patched/src/nmath/i1mach.c	2024-09-10 17:45:07.088808507 +0200
@@ -1,7 +1,7 @@
 /*
  *  Mathlib - A Mathematical Function Library
  *  Copyright (C) 1998  Ross Ihaka
- *  Copyright (C) 2000-7 The R Core Team
+ *  Copyright (C) 2000-2024 The R Core Team
  *
  *  This program is free software; you can redistribute it and/or modify
  *  it under the terms of the GNU General Public License as published by
@@ -51,7 +51,7 @@
     }
 }
 
-int F77_NAME(i1mach)(int *i)
+int F77_SUB(i1mach)(int *i)
 {
     return Rf_i1mach(*i);
 }
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/nmath/lgammacor.c R-patched/src/nmath/lgammacor.c
--- R-release-orig/src/nmath/lgammacor.c	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/nmath/lgammacor.c	2024-08-05 17:45:08.527645623 +0200
@@ -25,11 +25,12 @@
  *  DESCRIPTION
  *
  *    Compute the log gamma correction factor for x >= 10 so that
+ *                                               ---------
  *
  *    log(gamma(x)) = .5*log(2*pi) + (x-.5)*log(x) -x + lgammacor(x)
  *
- *    [ lgammacor(x) is called	Del(x)	in other contexts (e.g. dcdflib)]
- *
+ *    [ lgammacor(x) is called	Del(x)	in other contexts (e.g. dcdflib)], or  stirlerr(x)
+ *				~~~~~~					       ~~~~~~~~~~~
  *  NOTES
  *
  *    This routine is a translation into C of a Fortran subroutine
@@ -68,18 +69,20 @@
  *   xmax = DBL_MAX / 48 =  2^1020 / 3 */
 #define nalgm 5
 #define xbig  94906265.62425156
-#define xmax  3.745194030963158e306
 
     if (x < 10) // possibly consider stirlerr()
 	ML_WARN_return_NAN
+#ifndef IEEE_754
+#   define xmax  3.745194030963158e306
     else if (x >= xmax) {
 	ML_WARNING(ME_UNDERFLOW, "lgammacor");
 	/* allow to underflow below */
     }
+#endif
     else if (x < xbig) {
 	double tmp = 10 / x;
 	return chebyshev_eval(tmp * tmp * 2 - 1, algmcs, nalgm) / x;
     }
-    // else, xbig <= x < xmax :
+    // x >= xbig
     return 1 / (x * 12);
 }
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/src/unix/sys-std.c R-patched/src/unix/sys-std.c
--- R-release-orig/src/unix/sys-std.c	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/src/unix/sys-std.c	2024-10-11 01:31:07.090058211 +0200
@@ -1005,8 +1005,12 @@
 	    err = res == (size_t)(-1);
 	    /* errors lead to part of the input line being ignored */
 	    if(err) {
+		/* Should re-set with a stateful encoding, but some iconv
+                   implementations forget byte-order learned from BOM.
+
 		Riconv(cd, NULL, NULL, &ob, &onb);
 		*ob = '\0';
+		*/
 		printf(_("<ERROR: re-encoding failure from encoding '%s'>\n"),
 		       R_StdinEnc);
 		strncpy((char *)buf, obuf, len);
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/tests/Examples/graphics-Ex.Rout.save R-patched/tests/Examples/graphics-Ex.Rout.save
--- R-release-orig/tests/Examples/graphics-Ex.Rout.save	2024-03-27 00:02:08.000000000 +0100
+++ R-patched/tests/Examples/graphics-Ex.Rout.save	2024-08-05 17:45:08.662712136 +0200
@@ -1,7 +1,7 @@
 
-R Under development (unstable) (2023-09-08 r85109) -- "Unsuffered Consequences"
-Copyright (C) 2023 The R Foundation for Statistical Computing
-Platform: aarch64-apple-darwin22.6.0
+R version 4.4.1 Patched (2024-07-31 r86978) -- "Race for Your Life"
+Copyright (C) 2024 The R Foundation for Statistical Computing
+Platform: x86_64-pc-linux-gnu
 
 R is free software and comes with ABSOLUTELY NO WARRANTY.
 You are welcome to redistribute it under certain conditions.
@@ -1720,6 +1720,11 @@
 > plot(1:10, exp(1:10), log = "y", main = "log =\"y\"", xlab = "xlab")
 > for(s in 1:4) mtext(paste("mtext(...,side=", s ,")"), side = s)
 > 
+> ##--- illustrating padj behavior :
+> plot(0, axes=FALSE, ann=FALSE, frame.plot=TRUE)
+> for(si in 1:4) mtext(c("padj=0", "-----------", "padj=1"),
++                      side = si, padj = c(0, 0.5, 1))
+> 
 > 
 > 
 > cleanEx()
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/tests/datetime.R R-patched/tests/datetime.R
--- R-release-orig/tests/datetime.R	2023-03-24 00:02:05.000000000 +0100
+++ R-patched/tests/datetime.R	2024-09-13 01:31:07.115259169 +0200
@@ -21,6 +21,7 @@
 as.POSIXct("2040-07-01 12:00")
 
 Sys.setenv(TZ = "EST5EDT")  # also pretty much portable.
+## However, tzdata 2024b changed this from EST to LMY (and by 238s)
 (z <- as.POSIXct("1848-01-01 12:00"))
 c(unclass(z))
 ## see comment above
diff -ru -P -x .mirror -x ls_lR -x Old R-release-orig/tests/datetime.Rout.save R-patched/tests/datetime.Rout.save
--- R-release-orig/tests/datetime.Rout.save	2023-03-24 00:02:05.000000000 +0100
+++ R-patched/tests/datetime.Rout.save	2024-09-13 01:31:07.167737375 +0200
@@ -1,7 +1,7 @@
 
-R Under development (unstable) (2022-03-19 r81942) -- "Unsuffered Consequences"
-Copyright (C) 2022 The R Foundation for Statistical Computing
-Platform: x86_64-pc-linux-gnu (64-bit)
+R Under development (unstable) (2024-09-12 r87140) -- "Unsuffered Consequences"
+Copyright (C) 2024 The R Foundation for Statistical Computing
+Platform: aarch64-apple-darwin23.6.0
 
 R is free software and comes with ABSOLUTELY NO WARRANTY.
 You are welcome to redistribute it under certain conditions.
@@ -48,10 +48,11 @@
 [1] "2040-07-01 12:00:00 BST"
 > 
 > Sys.setenv(TZ = "EST5EDT")  # also pretty much portable.
+> ## However, tzdata 2024b changed this from EST to LMY (and by 238s)
 > (z <- as.POSIXct("1848-01-01 12:00"))
-[1] "1848-01-01 12:00:00 EST"
+[1] "1848-01-01 12:00:00 LMT"
 > c(unclass(z))
-[1] -3849922800
+[1] -3849923038
 > ## see comment above
 > as.POSIXct("2040-01-01 12:00")
 [1] "2040-01-01 12:00:00 EST"

Places

File R-release.diff of Package R (Revision 0834f59f255673369742f058bf4a6bbc)

Places