Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!

Support ISO8859-1 for SAINT imports

Avatar

Level 10

11/2/10

For all non-english speaking countries you're facing the problem with non-ASCII characters like ü, é, ç, Æ, ...

Using Excel to manage campaign sheets or other SAINT files, you run into the problem that a European Excel per default saves ISO8859-1 and won't save UTF8 at all. Depending on the Excel version you might be able to save a unicode, but this also doubles the file size.

Would be great if ISO8859-1 could be supported by SAINT.

 

Additionally please don't accept ISO8859-1 files that have characters with charcode >127 in SAINT standard import. Those are treated as UTF-8 on the servers, but will produce unreadable characters, since ISO8859-1 != UTF-8.

Please also accept UTF-8 files with a BOM. If you use an other tool to save SAINT sheets that saves UTF with BOM, SAINT won't accept although valid UTF-8.

4 Comments

Avatar

Level 5

11/2/10

Hi Andreas,

 

just out of curiosity: do you have that issue with both web and ftp upload?

I have successfully uploaded some Russian characters via ftp.

 

so long

nic

Avatar

Level 10

11/3/10

nic,

 

just tested it. yes, FTP is having the same issues.

Which encoding did the file with the Russian characters have? Sure it was ISO8859-1?

 

//Andreas

Avatar

Level 2

6/14/15

When we encountered the issue a few weeks ago, Customer Care instructed us to convert the file to UTF-8 without BOM before uploading. This seems to work but it would be nonetheless an improvement to have ISO8859-1 support - updating our SAINT file is a mostly automated process without that extra manual step.