[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: experimental support for SPV files now available
From: |
Ben Pfaff |
Subject: |
Re: experimental support for SPV files now available |
Date: |
Sun, 2 Dec 2018 09:55:50 -0800 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Sun, Dec 02, 2018 at 11:43:25AM -0600, Alan Mead wrote:
> The page numbers look good. I emailed you off list with some samples
> that didn't translate.
>
> I also tried converting to text, which was a little wonky and I wanted
> to bring it to your attention. BTW, text output appears in my browser
> window and then I have to use the browser functionality to save it to a
> file. Inexplicably, I was unable to save the text to a file in Chrome
> (it went through he motions and then there was no file on my hard
> drive). I had to switch to Firefox to save it. And for all I know,
> Firefox caused the wonkiness or exacerbated it.
>
> Here's what the top of one of the converted output files looks like in
> Notepadd++ (on Windows):
>
>
>
> This syntax is in a "log" in the output. It looks like all the space
> characters are not ASCII 32 (0x20) but something else. I don't know
> today what "text" means (I guess it's fundamentally meaningless) but I
> was expecting ASCII text. Here's what those look like in a hex viewer:
Thanks for the report. I ran into a previous issue where SPSS was
saving every space as a non-breaking space. I guess it must use other
space variants sometimes too. Weird.
This seems to be specific to the particular SPV file, because after
converting a couple of SPV files to text I don't see that behavior.
Oddly, I don't seem to have the particular SPV file in question. If you
send it to me, I'll fix the problem.