XML Encoding UTF8 Issue

[mojerry2]

Ok, but this means changing my server settings as I don't have SAS installed locally.

What's the impact to change the encoding?

[jakarman]

When you are working With Eguide you could ask for running two dedicated app-servers one for old fashioned sbcs and one for dbcs with utf-8.

There are several good docs like: http://support.sas.com/resources/papers/Multilingual_Computing_with_SAS_94.pdf

and http://support.sas.com/resources/papers/AddingAdditionalSASWorkspaceServerstoSupportMultipleEncoding...

By that you can use the one as needed and avoiding all additional issues.  The language features with dbcs are not fully compatible with classic dbcs see:SAS(R) 9.4 National Language Support (NLS): Reference Guide, Third Edition  Not being told there is that using SAS/connect (9.3) it won't work with intermixing sbcs/dbcs sessions, this is added in 9.4. The cport/cimport also doesn't work when the byteness sbcs/dbcs (latnin-1/utf8) is different. This one is not solved with 9.4. That will block you accessing data data that was backed up that way.