Quote:
Originally Posted by Paz
Hi,
I was following this as I sometimes work in Turkish. I had a feeling utf-8 locally was the wrong route but can you share a little of what you did to resolve the problem?
|
I found an alternate way of dealing with the issue, so it's solved for the time being (but not completely as you'll see).
One thing I left out, because I wasn't sure if it'd be relevant, was that I also had the csv documents in xml format too (with UTF-8 encoding). Originally, I found the xml documents a bit harder to manipulate so I didn't bother with them. Plus, I also felt I was wasting valuable time.
I decided to go back to the xml documents out of frustration with the csv docs and "hoping" something different would happen. Interestingly, after tailoring the xml documents to my needs, I'm finding that the foreign characters are not creating problems after I've uploaded them using the plugin. I wish I could explain the reason for this, but I don't have a lot of experience working with these kinds of documents. The good news is, I suppose, learning from all the trial and error.