eturn value, " However, currently, the
NEWS item is for R-devel, not R 3.4.1 patched.
On Mon, 31/7/17, Martin Maechler wrote:
Subject: Re: [Rd] translateChar in NewName in bind.c
Cc: r-devel@r-project.org
Date: Monday, 31 July, 201
;s bind.c (so it only contains the two
official bug fixes PR#172(84|92) but I wonder if it is
desirable in this case.
I'm glad for further reasoning.
Given current "knowledge"/"evidence", I would not revert
R-patched to R 3.4.1's behavior.
Mar
'translateCharUTF8', that is also correct. It has an
effect for this example.
x <- 0
names(x) <- "\xe7"
Encoding(names(x)) <- "latin1"
res <- c(x)
Encoding(names(res))
charToRaw(names(res))
----
On Tue, 13/6/17, Tomas
Thanks, fixed in R-devel.
Best
Tomas
On 06/11/2017 02:30 PM, Suharto Anggono Suharto Anggono via R-devel wrote:
I see another thing in function 'NewName' in bind.c. In
else if (*CHAR(tag)) ,
'ans' is basically copied from 'tag'. Could the whole thing there be just the
following?
ans = tag;
It s
I see another thing in function 'NewName' in bind.c. In
else if (*CHAR(tag)) ,
'ans' is basically copied from 'tag'. Could the whole thing there be just the
following?
ans = tag;
It seems to me that it can also replace
ans = R_BlankString;
in 'else'; so,
else if (*CHAR(tag))
and
else
can be merged
In function 'NewName' in bind.c
(https://svn.r-project.org/R/trunk/src/main/bind.c), in
else if (*CHAR(base)) ,
'translateChar' is used. Should it be 'translateCharUTF8' instead? The end
result is marked as UTF-8:
mkCharCE(cbuf, CE_UTF8)
Other cases already use 'translateCharUTF8'.
_
