Closed dshkol closed 3 years ago
I can try and re-encode the data to see if it goes away. Hard to fix because none of our checks pick it up.
I’ll try something along these lines: data for non-ASCII characters
I've found the offending data, it's in CODE_TABLE
, as expected.
length(grep("NOT_ASCII", iconv(CODES_TABLE$status_code, "UTF-8", "ASCII", sub="NOT_ASCII"))) + length(grep("NOT_ASCII", iconv(CODES_TABLE$status, "UTF-8", "ASCII", sub="NOT_ASCII")))
[1] 23
I saw a thread on r-dev that suggests if the non-ascii chars are intentional we should just comment in our cran notes as such, but might have issues for portability.
Hard to believe that there is no way to include non-ascii characters in a way that works on all R platforms. I say we just go with that route.
Will leave as such with an explicit note in cran comments that this is intentioal.
https://cran.r-project.org/web/checks/check_results_cancensus.html