Displaying 20 results from an estimated 1000 matches similar to: "translateChar in NewName in bind.c"
2017 Jun 11
1
translateChar in NewName in bind.c
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 to be just
else .
--------------------------------------------
2017 May 09
0
source(), parse(), and foreign UTF-8 characters
On 09/05/2017 3:42 AM, Kirill M?ller wrote:
> Hi
>
>
> I'm having trouble sourcing or parsing a UTF-8 file that contains
> characters that are not representable in the current locale ("foreign
> characters") on Windows. The source() function stops with an error, the
> parse() function reencodes all foreign characters using the <U+xxxx>
> notation. I have
2017 May 09
1
source(), parse(), and foreign UTF-8 characters
On 09.05.2017 13:19, Duncan Murdoch wrote:
> On 09/05/2017 3:42 AM, Kirill M?ller wrote:
>> Hi
>>
>>
>> I'm having trouble sourcing or parsing a UTF-8 file that contains
>> characters that are not representable in the current locale ("foreign
>> characters") on Windows. The source() function stops with an error, the
>> parse() function
2017 Jun 30
1
Rprintf expected encoding
I'm trying to find information about how to use Rprintf with a UTF-8
encoded string, and I'm not sure what the right cross-platform usage is.
I found an earlier thread about this
(http://r.789695.n4.nabble.com/How-to-print-UTF-8-encoded-strings-from-a-C-routine-to-R-s-output-td4724337.html)
but it wasn't very helpful.
If I want to print a UTF-8 string, I can do one of the
2008 Jan 27
0
Character encodings and packages
Since R 2.5.0 it has been possible to declare the encodings of character
strings (at the level of individual elements of a character vector).
As a reminder, here is the announcement in NEWS
o R now attempts to keep track of character strings which are
known to be in Latin-1 or UTF-8 and print or plot them
appropriately in other locales. This is primarily intended
to make it possible
2010 Feb 22
1
shash in unique.c
Looking at shash in unique.c, from R-2.10.1 I'm wondering if it makes sense
to hash the pointer itself rather than the string it points to?
In other words could the SEXP pointer be cast to unsigned int and the usual
scatter be called on that as if it were integer?
shash would look like a slightly modified version of ihash like this :
static int shash(SEXP x, int indx, HashData *d)
{
2017 May 09
2
source(), parse(), and foreign UTF-8 characters
Hi
I'm having trouble sourcing or parsing a UTF-8 file that contains
characters that are not representable in the current locale ("foreign
characters") on Windows. The source() function stops with an error, the
parse() function reencodes all foreign characters using the <U+xxxx>
notation. I have added a reproducible example below the message.
This seems well within the
2017 Sep 14
0
special latin1 do not print as glyphs in current devel on windows
This particular issue has a simple fix. Currently, the "R_check_locale"
function includes the following code starting at line 244 in
src/main/platform.c:
#ifdef Win32
{
char *ctype = setlocale(LC_CTYPE, NULL), *p;
p = strrchr(ctype, '.');
if (p && isdigit(p[1])) localeCP = atoi(p+1); else localeCP = 0;
/* Not 100% correct, but CP1252 is a
2017 Sep 14
2
special latin1 do not print as glyphs in current devel on windows
This is a follow-up on my initial posts regarding character encodings on
Windows (https://stat.ethz.ch/pipermail/r-devel/2017-August/074728.html)
and Patrick Perry's reply
(https://stat.ethz.ch/pipermail/r-devel/2017-August/074830.html) in
particular (thank you for the links and the bug report!). My initial
posts were quite chaotic (and partly wrong), so I am trying to clear
things up a
2017 Sep 28
1
R 3.4.2 is released
The build system rolled up R-3.4.2.tar.gz (codename "Short Summer") this morning.
The list below details the changes in this release.
You can get the source code from
http://cran.r-project.org/src/base/R-3/R-3.4.2.tar.gz
or wait for it to be mirrored at a CRAN site nearer to you.
Binaries for various platforms will appear in due course.
For the R Core Team,
Peter Dalgaard
2017 Sep 28
1
R 3.4.2 is released
The build system rolled up R-3.4.2.tar.gz (codename "Short Summer") this morning.
The list below details the changes in this release.
You can get the source code from
http://cran.r-project.org/src/base/R-3/R-3.4.2.tar.gz
or wait for it to be mirrored at a CRAN site nearer to you.
Binaries for various platforms will appear in due course.
For the R Core Team,
Peter Dalgaard
2017 Aug 23
0
Error "translateCharUTF8' must be called on a CHARSXP Execution halted"
On 23.08.2017 12:02, Braun, Stefan wrote:
> Dear list,
>
> I installed R 3.3.2 on a Red Hat Linux Enterprise 7.3 machine by adding the EPEL-repository and then installing it via yum.
> R starts up and seems to be doing fine at first sight. However, when I try to list the files in a directory with the command
>
> files <-
2008 May 21
1
rawToChar(raw(0))
Hi,
right now we have (on R v2.7.0 patched (2008-04-23 r45466)) that:
> rawToChar(raw(0))
[1] ""
> rawToChar(raw(0), multiple=TRUE)
character(0)
Is this intended or should both return character(0)? Personally, I
would prefer that an empty input vector returns an empty output
vector. Same should then apply to charToRaw(), but right now we get:
> x <- character(0)
>
2009 Jun 16
1
Package Install "Design" fails on Ubuntu 8.04
Dear All,
I am running a Ubuntu 8.04 System and trying to install the
Design-package. Hmisc is already installed, all fortran compilers and a
Tex-Package are also on board. I searched the net and the help list for
analogue threads, but didn't find any.
Whenever I run the install.packages("Design")-Command, the following
error message shows up in the terminal window:
--
**
2017 Aug 23
2
Error "translateCharUTF8' must be called on a CHARSXP Execution halted"
Dear list,
I installed R 3.3.2 on a Red Hat Linux Enterprise 7.3 machine by adding the EPEL-repository and then installing it via yum.
R starts up and seems to be doing fine at first sight. However, when I try to list the files in a directory with the command
files <- list.files(path="/home/username/directory_name/", pattern="*.Rda",, full.names=T, recursive=FALSE)
I get
2018 Feb 17
1
writeLines argument useBytes = TRUE still making conversions
Of course, right after writing this e-mail I tested on my Windows
machine and did not see what I expected:
> charToRaw(before)
[1] c3 a9
> charToRaw(after)
[1] e9
so obviously I'm misunderstanding something as well.
Best,
Kevin
On Sat, Feb 17, 2018 at 2:19 PM, Kevin Ushey <kevinushey at gmail.com> wrote:
> From my understanding, translation is implied in this line of ?file
2018 Feb 17
0
writeLines argument useBytes = TRUE still making conversions
>From my understanding, translation is implied in this line of ?file (from the
Encoding section):
The encoding of the input/output stream of a connection can be specified
by name in the same way as it would be given to iconv: see that help page
for how to find out what encoding names are recognized on your platform.
Additionally, "" and "native.enc" both
2012 Jul 20
1
subRaw?
Hello, All:
Do you know of any capability to substitute more then one byte in
an object of class Raw?
Consider the following:
> let4 <- paste(letters[1:4], collapse='')
> (let4Raw <- charToRaw(let4))
[1] 61 62 63 64
> (let. <- sub('bc', '--', let4Raw))
[1] "61" "62" "63" "64"
> # no
2011 Feb 01
1
list.files() error message: 'translateCharUTF8' must be called on a CHARSXP
I'm using list.files() on my home directory, like this:
crnt.files <- list.files(dir.to.check, full.names=TRUE, all.files=TRUE,
recursive=TRUE)
With dir.to.check set to the full path to my home directory.
After a while I get:
Error in list.files(dir.to.check, full.names = TRUE, all.files = TRUE, :
'translateCharUTF8' must be called on a CHARSXP
This happens on one of my
2020 May 02
0
paste(character(0), collapse="", recycle0=FALSE) should be ""
>>>>> suharto anggono--- via R-devel
>>>>> on Fri, 1 May 2020 03:05:37 +0000 (UTC) writes:
> Without 'collapse', 'paste' pastes (concatenates) its arguments elementwise (separated by 'sep', " " by default). New in R devel and R patched, specifying recycle0 = FALSE makes mixing zero-length and nonzero-length arguments