We are currently testing Omeka for our photographic archive and are using CSV import.
Our metadata (mainly Description and Tags fields) contain Turkish caracters which are not rendered properly with UTF-8 encoding. When the CSV file is encoded ISO-8859-1, CSV import reports an error and does not process it.
Is there a way to tweak the plugin in order to allow a different encoding ?
Thanks for all your advice and ideas to help me solve this problem
When you say your characters aren't rendered properly in UTF-8, what do you mean? That Omeka's doing something wrong, or they're wrong within the file itself?
Hi John, I mean the Turkish caracters are not rendered properly in the file, i.e.
? instead of ı
$ instead of ş
and so on
Sorry to insist with the same issue, CSV import will not accept any other encoding than UTF-8 and since we are dealing with a 13,000+ collection of items, we would need a workaround. Editing by hand all Turkish descriptions one by one after import into Omeka does not seen very optimal.
I would also be glad to hear about any tweak allowing to batch import geolocation coordinates. I searched the forums but all I found is that it is currently not possible.
Has anyone ever dealt with a similar issue and would be willing to share his/her experience?
The reason I ask is, if they look wrong in the file itself, that would indicate some problem with the process you're using to create or convert the file, not with CSV Import.
UTF-8 is perfectly capable of displaying those Turkish characters (it's how they're being stored and displayed on these forums, for example); it's actually ISO 8559-1 that can't handle Turkish, since it doesn't include İ, ı, Ğ, ğ, Ş, or ş.