SS script backup & import: unicode characters aren't handled properly?

Hi guys,

I'm not sure if this is the right forum for this but here goes: I have a script that I use to parse through firm addresses for the U.S. and several countries in Europe, some of which (e.g., France, Germany and Sweden) contain words with unicode characters. Although I'm developing this script for 1 scrape, I'd like to implement it elsewhere to provide other scrapes w/the same address-parsing functionality.

I noticed that SS allows you to export a script from one scrape and then import it into another scrape provided the same script name is unused. This seemed like a solution except when I tried importing this script, words with unicode characters didn't come back with their appropriate encoding. For example, the Swedish city "Göteborg" in the original script would appear in the newly imported script as "G�teborg". Obviously, this wasn't what I was expecting when I imported the script...

A couple of additional things:
- when I look at the exported script in Notepad or Notepad++, I can see that the unicode characters appear correctly as long as I am using a unicode font.
- My SS settings are set to use UTF-8 as the character set and Arial Unicode MS as the default font.
- Other SS scripts containing unicode characters (including the original script from which the imported is derived) appear properly.

So my questions are:
a) when you import (or even re-import) a script w/unicode, why aren't the unicode characters imported properly?
b) is there a workaround for importing scripts with unicode characters? (e.g., copy/paste from a WordPad doc?)

Thanks very much in advance for any help you can provide!

Regards,
Justin

Unicode in scripts is both

Unicode in scripts is both rare and difficult, so we've always resorted to replacing unicode charaters with their code.

The letter "ö" would be "/u00d6". You can see the codes here

Thanks and more unicode weirdness

Hi Jason,

Thanks for that info - it's probably good practice going forward. I also wanted to let you know that when I export the scrape to which this script belongs and then re-import it on another computer, the unicode appears to come in properly. So it seems to be only when I re-import the script by itself that the unicode gets lost in translation.
(Not sure why that is, but hey, maybe it will help someone else...)

We'll investigate, and see if

We'll investigate, and see if there is a difference in handling sessions versus scripts.

Superthanks!