#15 Swedish characters (едц) not handled properly

[Jimisola Laursen]

Using:
- Outport 1.1.25
- MS Office 2003 (XP)
- Ximian Evolution 1.4.4

Swedish characters (and I guess characters in other
languages) are not handled correctly when exporting
directly to Evolution format. If exporting to a .vcf then
characters still exists after import. However, Evolution
does not like files with these characters in file names..

Jimisola

[Paul Thompson]

Logged In: YES
user_id=641281

Yeh, Outport is really bad at handling non-English
characters. I've made a few attempts at doing this properly,
but it is difficult with the current code-base. I will get
back to the problem.

[Jimisola Laursen]

Logged In: YES
user_id=935333

This bug is a real pain as it makes Output useless on a day-to-
day basis. After each Export I have to go through all my
Contacts manually and correct those with "special" characters.

Would love to see this problem getting solve. I don't know
what it takes, but Unicode sounds good :)

Regards,
Jimisola

[Nobody/Anonymous]

Logged In: NO

Is this only for characters in file names? Why are there
filenames with Swedish characters?

Evolution expects filenames in UTF-8 unless you set env
G_FILENAME_ENCODING=iso-8859-1 . Perhaps this is getting you
into trouble?

[Palle Girgensohn]

Logged In: YES
user_id=11735

OK, I should have read the entire contents of this bug, sorry!

Exactly HOW are the characters bad? They should be in the
UTF-8 chacter set. Which are they in? Is it a mix? How do
they look like?

My guess is that outlook uses cp1252 (almost identical to
iso8859-1).

have you tried iconv for converting the output from outport?

http://gettext.sf.net/

$ echo | iconv -f iso-8859-1 -t utf-8
åäö

I need this working as well. A user reported that mozilla
*can* read a calendar file from outport, but our
application, that expects UTF-8, cannot. I don't have a
windows machine around to test this today, but from the logs
of our application, it looked like it was a mix of character
sets, although I'm not sure, really. The character 0x00ef (
in latin-1) was the only char it complained about, and it
expects UTF-8. Hmm... Will test more once I find a windows
machine.