London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
I do not know if what you are asking is possible, but you could always change the encoding from UTF-8 to ANSI (for example, using Notepad) before uploading.
Yes I did that. And that works as a workaround. I just think Optimizely should fix this in their export logic, so I do not have to remember to use this workaround every time. (The first time I didn't, and then I have to clean up).
When exporting synonyms from /EPiServer/Find/#optimize can you change the character set the file is created with, from UTF-8 to ASCII. This will make think easier when I (I'm Norwegian) imports the synonyms because we have synonyms with æøå!