On 05/08/2019 2:13 p.m., Roy Mendelssohn - NOAA Federal wrote:
Okay I found it. I looked at the code for tools:::.check_package_datasets(),
took out the core part, ran every string I had in every dataset, it came
out. A degree symbol.
Thanks for telling me about the function. Still sur
Okay I found it. I looked at the code for tools:::.check_package_datasets(),
took out the core part, ran every string I had in every dataset, it came
out. A degree symbol.
Thanks for telling me about the function. Still surprised that the test
machines don't flag it. Or is this a new t
Using tools:::.check_package_datasets() produces the error, but doesn't give
out any more information. I don't know enough about some fo the write()
function. If I write to csv of some sort, will this information be preserved?
Thanks,
-Roy
> On Aug 5, 2019, at 8:57 AM, Roy Mendelssohn - N
Thanks. What is surprising me is I can't reproduce the error either directly
on my Mac or on rhub::windows and I am waiting for the result of win-builder
(I can't check most rhub::linux because it fails to correctly build a number
of required packages, something I have reported but still per
On 05/08/2019 10:51 a.m., Roy Mendelssohn - NOAA Federal via
R-package-devel wrote:
Hi All:
The recent nighty CRAN checks on one of my packages reports:
Check: data for non-ASCII characters
Result: NOTE
Note: found 1 marked UTF-8 string
When originally submitted this was not the case.
