Interesting. 'Kruskal Wallis' gets 5.68M google hits, 'Kruskall
Wallis' gets 432K ...
Within CRAN packages, sos::findFn("kruskal") gets 408 hits,
=sos::findFn("kruskall") gets 15 hits. (Some of those may be like the
use of 'euclidian' in stats::dist() to intentionally match misspellings
...
Further to my earlier email,
I understand that my package has been archived since my last version on CRAN
(1.1.0) had among its dependencies a package that has been archived.
Now my question:
How can I bring my package (actually the new version 1.1.1 that I’m trying to
check) back to life (i.e.
Hello,
After checking my package with win builder, I got 1 note that I seem to not
fully understand:
CRAN repository db overrides:
X-CRAN-Comment: Archived on 2020-03-17 as depends on archived package
'spatialEco'.
Do you have any suggestion?
There is not reference to that package in my NAM
However, notice that if it is the guy from the Kruskal-Wallis test (William K.,
1919--2005), the "Kruskall" is in fact misspelt. It might be someone else, of
course...
-pd
> On 17 Mar 2020, at 18:24 , Duncan Murdoch wrote:
>
> I believe it is also acceptable to explain in your submission mess
I believe it is also acceptable to explain in your submission message
that the misspelled words are all proper names. As far as I know,
misspellings are not enough of a problem to cause an automatic
rejection, so a human being will be making a judgment about the note.
Duncan Murdoch
On 17/03
You can single quote them to avoid them being spell checked, e.g. ...
using methods of 'Kruskall' and 'Brainerd'. This is a common and
accepted practice.
This is hinted at in "Writing R Extensions" (e.g. help.start());
The mandatory ‘Description’ field should give a comprehensive
description of
Hello,
I am checking a package of mine, and I got only 1 note regarding possibly
misspelled words in the DESCRIPTION.
The issue I am facing is that those 6 words are not actually misspelled, being
either first or last names of individuals (actually, statistician; e.g.,
Kruskall, Brainerd).
Sha
Hi r-package-devel,
CRAN asked me to correct some errors so I'm currently in the process of
updating/ resubmitting my package and ran into an error connected to one of my
dependencies.
The thing is that the problem only occurs during the r-devel checks because of
a newer package version of said
