Lucy
--
-- To post, send email to arches...@googlegroups.com. To unsubscribe, send email to archesprojec...@googlegroups.com. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en
---
You received this message because you are subscribed to the Google Groups "Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archesprojec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
From: Alexei PetersTo: Lucy FJCc: Arches ProjectSent: Wednesday, January 20, 2016 8:24 PMSubject: Re: [Arches] Diacriticals in authority and .Arches files problems
Hi Lucy,
as far as I know Excel (all versions) are notoriously bad at handling things like character encodings. This rather old Stackoverflow question seems to confirm that:
http://stackoverflow.com/questions/4221176/excel-to-csv-with-utf8-encoding It does offer some workarounds, but none of them are very nice.
I would suggest writing your CSV files with Libreoffice/Openoffice. You should be able to install it and it's free. While it's not always an exact replacement for Excel, when it comes to character encodings, it just works. By default it will save things as UTF-8 (at least under Linux it does) and it will ask you if you want to save in a different encoding.
Cheers,
Koen
Hi Lucy,
character encodings are one of those nasty issues in computing that nobody likes tackling. If you want a detailed, yet fairly easy to follow analysis on why that is, see
http://www.joelonsoftware.com/articles/Unicode.html (Cthulhu is waiting for you there though...)
Basically, what Arches does is the best thing possible. That way most human languages can be integrated in Arches, and all you need to do is make sure your data is UTF-8. Unfortunately Excel makes that bloody impossible. I think Excel saves that file in
the ISO-8859-1 encoding. That encoding just doesn't know the characters you're trying to save (ISO-8859-1 only contains 191 characters). So, it's not just Arches. I can't read them either. Excel should be telling you when saving as CSV that you will lose
information), it still wouldn't work since your csv file already contains illegal ISO-8859-1 characters.
And it's not just Excel, the whole Windows ecosystem is fundamentelly flawed in that regard. I myself run Linux where character encoding is handled correctly and UTF-8 is the default. No idea how they do it on a Mac.
So, I think using OpenOffice is your best bet. Or just open the csv file you have in Notepad++ (or similar text editor), save the file as UTF-8 and fix the problems manually. But then you'd have to do that every time you want to change something.
Cheers,
Koen
You received this message because you are subscribed to a topic in the Google Groups "Arches Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/archesproject/3l6N7KuEpXY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to archesprojec...@googlegroups.com.