|
| From: | Kees Varekamp |
| Subject: | Re: running syntax file from ui vs running syntax file from command prompt |
| Date: | Thu, 10 Apr 2014 16:26:09 +1200 |
Well, I solved the problem for you, but it's still terrifically confusing and in the long run we need some better approach, so I'll try to keep thinking about it.
On Apr 9, 2014 8:42 PM, "Kees Varekamp" <address@hidden> wrote:KeesYou are completely right - it looks fine now!Awesome, thanks.On Thu, Apr 10, 2014 at 3:27 PM, Ben Pfaff <address@hidden> wrote:
On Wed, Apr 09, 2014 at 09:09:28PM +1200, Kees Varekamp wrote:
> I am trying to run a utf-8 syntax script in PSPP 0.8.2 on win7 64bit, but I> log.txt--syntax-encoding=utf-8
> think there is a problem when I run the a syntax file from the command line:
> --syntax-encoding as a start param does not seem to work:
>
> I have tried:
> "C:\Program Files\PSPP\bin\pspp.exe" file.sps -b -o
> log.txt--syntax-encoding=UTF-8
> "C:\Program Files\PSPP\bin\pspp.exe" file.sps -b -o
> "C:\Program Files\PSPP\bin\pspp.exe" file.sps -b -o> log.txt--syntax-encoding=UTF8
> "C:\Program Files\PSPP\bin\pspp.exe" file.sps -b -o
> log.txt--syntax-encoding="UTF-8
> "
> "C:\Program Files\PSPP\bin\pspp.exe" --syntax-encoding="UTF-8" file.sps -bThe encoding of a syntax file is independent of the encoding of the
> -o log.txt
>
> All with no success - my Thai characters get garbled. However, when I load
> the script through the gui (and select UTF-8 from the dialog) it works
> perfectly. So I think this command line param just doesn't work.
active file. --syntax-encoding controls the former. "SET LOCALE"
controls the latter. If you add "SET LOCALE='utf-8'" to the top of your
syntax file, it ought to work as expected. (Both encodings default to
the system locale, so switching to a UTF-8 locale should also work.)
--Kees VarekampMROffice Director44 Castleford street, 0604, Auckland, New ZealandPhone: +6492821656Skype: kees.mrofficeMROffice - Meeting Market Research Needs
| [Prev in Thread] | Current Thread | [Next in Thread] |