I think it is as Kevin described in an earlier response - the garbled
output is because a UTF-8 encoded string is assumed to be native
encoding (which happens not to be UTF-8 on the platform where this is
observed) and converted again to UTF-8.
I think the documentation is consistent with th
Thank you for the report and analysis. Now fixed in R-devel.
Tomas
On 02/17/2018 08:24 PM, William Dunlap via R-devel wrote:
I think the problem in R-devel happens when there are non-ASCII characters
in any
of the strings passed to gsub.
txt <- vapply(list(as.raw(c(0x41, 0x6d, 0xc3, 0xa9, 0x6c,
Dear R-Devel List,
I have installed R 3.4.3 with the patch applied on our cluster and ran a
*real-world* job of one of our users to confirm that the patch works to my
satisfaction. Here are the results.
The original was a series of jobs, all essentially doing the same stuff using
bootstrapped
Hi, I'm trying to understand the rationale for your proposed amount of
splitting and more precisely why that one is THE one.
If I put labels on your example numbers in one of your previous post:
nbrOfElements <- 97
nbrOfWorkers <- 5
With these, there are two extremes in how you can split up th
