Hi,
I was unable to find a bug report for this with a cursory search, but would
like clarification if this is intended or unavoidable behaviour:
```{r}
# Create example data.frames
parents <- data.frame(name=c("Sarah", "Max", "Qin", "Lex"),
sex=c("F", "M", "F", "M"),
Hi
I have committed the suggested "extern" patch.
Could you please confirm that this fixes the issue on Solaris (and
anything else you can test) ?
Thanks!
Paul
On 16/02/18 03:39, dmitrii.pasech...@maths.ox.ac.uk wrote:
Dear all,
in src/include/GraphicsBase.h one has a declaration
int base
On Thu, Feb 15, 2018 at 11:19 AM, Kevin Ushey wrote:
> I suspect your UTF-8 string is being stripped of its encoding before
> write, and so assumed to be in the system native encoding, and then
> re-encoded as UTF-8 when written to the file. You can see something
> similar with:
>
> > tmp <- '
I suspect your UTF-8 string is being stripped of its encoding before
write, and so assumed to be in the system native encoding, and then
re-encoded as UTF-8 when written to the file. You can see something
similar with:
> tmp <- 'é'
> tmp <- iconv(tmp, to = 'UTF-8')
> Encoding(tmp) <- "
Dear all,
in src/include/GraphicsBase.h one has a declaration
int baseRegisterIndex;
the same as in src/main/devices.c
which causes problems on Solaris, see bug #17385,
and other platforms with "unusual" linkers, see bug #16633.
By right, global variables like baseRegisterIndex are to be
decla
I think this behavior is inconsistent with the documentation:
tmp <- 'é'
tmp <- iconv(tmp, to = 'UTF-8')
print(Encoding(tmp))
print(charToRaw(tmp))
tmpfilepath <- tempfile()
writeLines(tmp, con = file(tmpfilepath, encoding = 'UTF-8'), useBytes = TRUE)
[1] "UTF-8"
[1] c3 a9
Raw text a
