Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn

Hi. Just so I am clear, how do you know that it is codepage encoding? Do you have UNICODE OFF?

If so, then the file will be treated as non-UTF8.

Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn

When I select the file in File, Open, Syntax, the dialog automatically switches to "declarated" ("Wie deklariert" in german), and the file is shown correct. But when I select the file in Windows Explorer, there is no choice of encoding and umlauts are shown incorrect. Unicode is always ON.

I personally use Notepad++ for editing and check the file encoding there. This is also the reason a lot of files without BOM exist, as I didn't set it. We always assumed the declaration line has priority in SPSS and wondered about the resulting mess.

Hi. Just so I am clear, how do you know that it is codepage encoding? Do you have UNICODE OFF?

If so, then the file will be treated as non-UTF8.

Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn

In Notepad++, could you change from UTF-8 to UTF-8-BOM and see if that makes a difference?

When I select the file in File, Open, Syntax, the dialog automatically switches to "declarated" ("Wie deklariert" in german), and the file is shown correct. But when I select the file in Windows Explorer, there is no choice of encoding and umlauts are shown incorrect. Unicode is always ON.

I personally use Notepad++ for editing and check the file encoding there. This is also the reason a lot of files without BOM exist, as I didn't set it. We always assumed the declaration line has priority in SPSS and wondered about the resulting mess.

Hi. Just so I am clear, how do you know that it is codepage encoding? Do you have UNICODE OFF?

If so, then the file will be treated as non-UTF8.

Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn

Yes it does. Files with BOM always are displayed correct.

In Notepad++, could you change from UTF-8 to UTF-8-BOM and see if that makes a difference?

When I select the file in File, Open, Syntax, the dialog automatically switches to "declarated" ("Wie deklariert" in german), and the file is shown correct. But when I select the file in Windows Explorer, there is no choice of encoding and umlauts are shown incorrect. Unicode is always ON.

I personally use Notepad++ for editing and check the file encoding there. This is also the reason a lot of files without BOM exist, as I didn't set it. We always assumed the declaration line has priority in SPSS and wondered about the resulting mess.

Hi. Just so I am clear, how do you know that it is codepage encoding? Do you have UNICODE OFF?

If so, then the file will be treated as non-UTF8.

Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn

Good!

The commented line with UTF-8 (or not) isn't a definitive instruction to the program on how to treat the file; the byte-order-mark is.

We should make the syntax editor more intelligent and robust in this regard, no doubt, but at least for the time being be sure when in Notepad++ to save with the BOM and you should be fine.

Yes it does. Files with BOM always are displayed correct.

In Notepad++, could you change from UTF-8 to UTF-8-BOM and see if that makes a difference?

When I select the file in File, Open, Syntax, the dialog automatically switches to "declarated" ("Wie deklariert" in german), and the file is shown correct. But when I select the file in Windows Explorer, there is no choice of encoding and umlauts are shown incorrect. Unicode is always ON.

I personally use Notepad++ for editing and check the file encoding there. This is also the reason a lot of files without BOM exist, as I didn't set it. We always assumed the declaration line has priority in SPSS and wondered about the resulting mess.

Hi. Just so I am clear, how do you know that it is codepage encoding? Do you have UNICODE OFF?

If so, then the file will be treated as non-UTF8.

Hello,

we have several syntax documents with declaration "* Encoding: UTF-8.", but without BOM. When we open such a document from Windows Explorer with double click, the SPSS editor unexpectedly uses codepage encoding. This led to some confusion.

Regards, fdsbonn