On Tue, 2005-03-29 at 14:12 +0200, Armin Bauer wrote: 
> ah. now it makes sense :)
> 
> so evolution2 gets a vcard that is iso-8859-1 encoded. from the manpage:
> 
> E9           LATIN SMALL LETTER E WITH ACUTE
> 
> so i think the correct approach to this would be to fix in the other 
> plugin since all vcards passing through multisync should be encoded in utf8.
> 
> Another possibility would be to use g_utf8_validate in the evo2 plugin 
> and if it returns false use g_convert from iso-8859-1 to utf8. But this 
> would just be a ugly hack.

Ok, I think I got you. One other question: I tried fiddling around with
the value for "Translate from character set" in "Bug Workarounds" in the
IrMC plugin (the "other" plugin); I did this:

1. Set it to a given value (tried with UTF-8 and ISO-8859-1).
2. Erased the calendar.ics-msyncid2.db and all appointments in the
phone's calendar.
3. Synchronized once; it worked.
4. Synchronized again; it didn't work.

Do you think this setting could have any impact in my problem? If yes,
is there any other value, other than UTF-8 and ISO-8859-1, that I should
try here?

Regards.


-- 
Gonzalo Diethelm
[EMAIL PROTECTED]



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Multisync-users mailing list
Multisync-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/multisync-users

Reply via email to