utf-8 characters under iOS with vcard 3.0

[Alex]

Hi all,

last month I switched my windows mail program to emClient, since under Win it is the only clean solution for Carddav and Caldav (at least compared to the maintenance cycles of Thunderbird and postbox). 

Anyway, as Sabredav and emClient both support utf8 and vcard 4.0, all carddav contacts are stored on the server like this. Once one opens these contacts under iOS, the utf-8 characters are wrongly displayed/converted (e.g. German umlauts). 

The developers of emClient identified the conflict as the cards being stored in version 4.0, but iOS does only support up to carddav 3.0.

Would you agree on the explanation and how to solve it? I searched for a function in the API to switch the server to carddav 3.0, but couldn't make it.

btw: iOS setup with sabredav running only on HTTP and not HTTPS is quite slow (5 mins to switch to HTTP). I have the .well-known in the rewrite rules

# Redirect /.well-known URLs

RewriteRule ^/(.*)$ /server.php [L]

Maybe also one can help me?

Thank you!

[Evert Pot]

On Friday, June 14, 2013 7:54:01 PM UTC+1, Alex wrote:

Hi all,

last month I switched my windows mail program to emClient, since under Win it is the only clean solution for Carddav and Caldav (at least compared to the maintenance cycles of Thunderbird and postbox). 

Anyway, as Sabredav and emClient both support utf8 and vcard 4.0, all carddav contacts are stored on the server like this. Once one opens these contacts under iOS, the utf-8 characters are wrongly displayed/converted (e.g. German umlauts). 

You need to switch to vCard 3. Older versions of SabreDAV advertised vCard 4.0 support, but looking back this was a bad idea. If you run any supported SabreDAV version vCard 4.0 is no longer advertised as supported, and this should fix the umlaut issues.

In the future I plan to add vCard 4 support again, but I can only do this if I automatically convert the vCards back to 3, if a client doesn't specifically request vCard 4.
 

The developers of emClient identified the conflict as the cards being stored in version 4.0, but iOS does only support up to carddav 3.0.

Would you agree on the explanation and how to solve it? I searched for a function in the API to switch the server to carddav 3.0, but couldn't make it.

Yea.. so.. upgrade. This was fixed in 1.8.3, 1.7.5 and 1.6.7.
 

btw: iOS setup with sabredav running only on HTTP and not HTTPS is quite slow (5 mins to switch to HTTP). I have the .well-known in the rewrite rules

# Redirect /.well-known URLs

RewriteRule ^/(.*)$ /server.php [L]

Maybe also one can help me?

Perhaps your firewall is configured to drop any packets going to unknown ports. The effect would be that the client waits till the tcp packets time out.

The best solution is of course to switch to HTTPS. Certificates are cheap, it's worth it..

Evert

[Alexander]

Hi Evert,

ok thanks a lot. With Diff I also was able to find the source line for Vcard3/4... Now the update to 1.8.5 fixed all issues.

Evert Pot

Samstag, 15. Juni 2013 14:39

--
You received this message because you are subscribed to a topic in the Google Groups "SabreDAV Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sabredav-discuss/_3SEi_Tnlts/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sabredav-discu...@googlegroups.com.
To post to this group, send email to sabredav...@googlegroups.com.
Visit this group at http://groups.google.com/group/sabredav-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Stefan]

Hi,

I ran into the same problems and need to disable Vcard4 support, as I'm working with eM Client and IOS and I have problems with german umlaut characters.

But I have a Baikal Package provided from Netgear vor ReadyNAS OS6 installed on my NAS, so I cannot upgrade to a newer SABRE version I think.
There is v1.8.0-stable used, so any chance that I can apply a patch to disable VCard4?

Thanks
Stefan

[Evert Pot]

If you are able to apply a patch, you should also be able to do a full upgrade.

1.8.0 is over 2 years old. 1.8.11 is 100% compatible with that version, but has numerous bugfixes and also a several security fixes.

Evert