Issue 26931

Summary: OOo Contact connection to Evolution is loosing accented characters
Product: Base Reporter: lsafar <lsafar>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, mkretzschmar
Version: OOo 1.1.1RC   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Output of: evolution-addressbook-export --format=csv --output=addresses.csv none

Description lsafar 2004-03-24 16:09:38 UTC 
I've created new data source in OOo, which is of contact type with evolution as
source.

Accented characters in evolution database don't survive - i.e. "á" is converted
to "/303/241", "í" is converted to "/303/255". 
I would guess it has something to do with Evolution (1.4.5) storing information
in UTF-8, but not sure.
Comment 1 marc.neumann 2004-03-26 11:06:21 UTC 
hi,

I can reproduce this.

msc -> windly: the evolution-addressbook-export export the values correct, so I
believe it's the OOo driver.

Bye Marc
Comment 2 wind.li 2004-03-26 15:19:52 UTC 
Cah you please attachment the exported file?
Comment 3 lsafar 2004-03-29 11:01:06 UTC 
Created attachment 14143 [details]
Output of: evolution-addressbook-export --format=csv --output=addresses.csv
Comment 4 lsafar 2004-03-29 11:04:26 UTC 
I've attached some output where the characters appear as well.
It looks like the main problem is that UTF-8 gets escaped during export, there
are two character expected in name "á" and "ý".
Comment 5 lsafar 2004-04-19 15:38:26 UTC 
I've used perl oneliner to unescape output and it works OK - output is an
unicode text, import as such to OOo works OK.

evolution-addressbook-export --format=csv | perl -pe 's/\\([0-7]{1,3})/chr oct
"$1"/ge'

Would it be possible to unescape automatically during import?
Comment 6 mkretzschmar 2004-04-20 09:25:20 UTC 
This was already mentioned in bug 20958

I believe that octal-escaping utf-8-encoded unicode is wrong, so I wrote a patch
for evolution last October to not do that.

At that time I was thinking that
http://bugzilla.ximian.com/show_bug.cgi?id=49519 might be handled reasonably
fast. Unfortunately it wasn't.

At this point of the evolution 1.4 product lifetime (and as the db connection
for evolution 1.5/2.0 is almost done AFAIK), it's probably better to add the
unescaping code on the OOo side.
Comment 7 wind.li 2005-03-23 08:59:56 UTC 
working transfer
Comment 8 Frank Schönheit 2005-05-10 13:57:54 UTC 
targeting
Comment 9 Marcus 2017-05-20 10:45:02 UTC 
Reset the assignee to the default "issues@openoffice.apache.org".