You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess you get the idea. The collaborator has saved the sav-file in utf-8 by adding a line SET UNICODE = ON. to his/her syntax-file. My locals are set to utf-8, too.
I am using the uxterm terminal-emulator for running R. Thus, everything is in utf-8. I have the strong suspicion that memisc is using a latin1 encoding when parsing the SPSS sav-file by default. Is this correct? Is it possible to change this encoding when parsing?
Thanks you very much!
PS. Why does it say 27 of 379 observations shown, when in fact only 25 of them are shown?
The text was updated successfully, but these errors were encountered:
spss.system.file() reads strings contained in SPSS files as-is, without any translation. The resulting strings therefore do not contain any encoding information. My guess is that this is why you see that strange output. So far, I did not encounter a problem like the one you describe, since most SPSS files I encountered were in latin1. However, memisc now has a function Iconv() for explicit translation of SPSS data files. Does
Dear Martin,
I have been given a SPSS system file that I would like to analyse using R. I am using the following magic for parsing the file into R.
When having a look at the parsed data, you get the following:
I guess you get the idea. The collaborator has saved the sav-file in utf-8 by adding a line
SET UNICODE = ON.
to his/her syntax-file. My locals are set to utf-8, too.I am using the
uxterm
terminal-emulator for running R. Thus, everything is in utf-8. I have the strong suspicion thatmemisc
is using alatin1
encoding when parsing the SPSS sav-file by default. Is this correct? Is it possible to change this encoding when parsing?Thanks you very much!
PS. Why does it say 27 of 379 observations shown, when in fact only 25 of them are shown?
The text was updated successfully, but these errors were encountered: