At 06:25 09.11.2008, Prof Brian Ripley wrote:
On Sat, 8 Nov 2008, Heinz Tuechler wrote:
At 08:01 08.11.2008, Prof Brian Ripley wrote:
We have no idea what you understood (you didn't tell us), but the help says
encoding: character vector. The encoding(s) to be assumed when 'file'
is
At 08:01 08.11.2008, Prof Brian Ripley wrote:
We have no idea what you understood (you didn't tell us), but the help says
encoding: character vector. The encoding(s) to be assumed when 'file'
is a character string: see 'file'. A possible value is
'unknown': see the
On Sat, 8 Nov 2008, Heinz Tuechler wrote:
At 08:01 08.11.2008, Prof Brian Ripley wrote:
We have no idea what you understood (you didn't tell us), but the help says
encoding: character vector. The encoding(s) to be assumed when 'file'
is a character string: see 'file'. A possible
Heinz Tuechler wrote:
Dear Prof.Ripley!
Thank you very much for your attention. In the given example Encoding(),
or the encoding parameter of read.csv solve the problem. I hope your
patch will solve also the problem, when I read a spss file by
spss.get(), since this function has no encoding
At 13:34 07.11.2008, Peter Dalgaard wrote:
Heinz Tuechler wrote:
Dear Prof.Ripley!
Thank you very much for your attention. In the given example Encoding(),
or the encoding parameter of read.csv solve the problem. I hope your
patch will solve also the problem, when I read a spss file by
On Fri, 7 Nov 2008, Peter Dalgaard wrote:
Heinz Tuechler wrote:
Dear Prof.Ripley!
Thank you very much for your attention. In the given example Encoding(),
or the encoding parameter of read.csv solve the problem. I hope your
patch will solve also the problem, when I read a spss file by
At 16:52 07.11.2008, Prof Brian Ripley wrote:
On Fri, 7 Nov 2008, Peter Dalgaard wrote:
Heinz Tuechler wrote:
Dear Prof.Ripley!
Thank you very much for your attention. In the given example Encoding(),
or the encoding parameter of read.csv solve the problem. I hope your
patch will solve also
We have no idea what you understood (you didn't tell us), but the help
says
encoding: character vector. The encoding(s) to be assumed when 'file'
is a character string: see 'file'. A possible value is
'unknown': see the ‘Details’.
...
This paragraph applies if 'file'
Dear All!
Reading character strings containing an umlaut
from a csv-file I find a (to me) surprising
behaviour in R 2.8.0, that I did not notice in R 2.7.2.
A comparison by == results in FALSE, while grep does find the aggreement.
See the example below.
The crucial line is x==div 1-2
Look at Encoding() on your two strings. The results are different, and
this seems to be the root of the problem. Adding encoding=latin1 to the
read.csv call is a workaround.
It looks like there is a problem in the use of the CHARSXP cache: if I
save the session then x0 == x becomes true
Dear Prof.Ripley!
Thank you very much for your attention. In the
given example Encoding(), or the encoding
parameter of read.csv solve the problem. I hope
your patch will solve also the problem, when I
read a spss file by spss.get(), since this
function has no encoding parameter and my real
11 matches
Mail list logo
