-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More robust handling of not-well-formatted files #217
Comments
Hi, it would help to have an example file demonstrating the issue that I can test against. Thanks. |
with thanks |
evanmiller
added a commit
that referenced
this issue
Sep 30, 2020
@jonathon-love Please try the |
all good. thanks evan! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi evan,
i had some people contact me about the spss files they were writing, not being able to be read by jamovi (and by extension, readstat ... or is it the other way around?), however, these files could be read by spss. the error message was:
Error parsing string "Var1=Var1 Var2=Var2 Var3=Var3 Var4=Var4 Var5=Var5 Q1=Q1" around byte #1/55, character a
i believe the error is the
a
inVar1=
... where i think ReadStat expects the name before the=
to be all uppercase (and i think spss automagically 'upgrades' these to be uppercase if you open and resave the file).am i correct in what i'm thinking?
which leads to a follow-up question ... what about ReadStat handling these files the same way spss does?
with thanks
The text was updated successfully, but these errors were encountered: