Accented characters do not display correctly in Windows Contacts and Outlook.

Characters like ýeèóõ display as ýeèóõ. To be honest, I have no idea why this does not work. It appears to be an encoding issue, but as far as I can see everything is properly encoded using UTF-8. Importing it in Google Contacts works flawless.

So it might as well be a long standing bug in Windows (This was already reported for Windows 7 in 2011).

If I deliver the file with windows-1252 or ISO-8859-1 encoding it works, but that would go against the VCARD 4.0 specification in rfc6350 (paragraph 3.1), which states the only right encoding type is UTF-8. Besides I have no idea how Windows specific encodings would work on mac and Linux.

So I am stuck here. Anybody who has ideas is welcome to share them.

CommentFileSizeAuthor
#2 special-characters-2866862-2.patch1.35 KBsludwig

Comments

Neograph734 created an issue. See original summary.

sludwig’s picture

StatusFileSize
new1.35 KB

Please try the attached patch for the template-file. With adding CHARSET=utf-8 to the fields, most contact- / mail-clients can be additionally forced to interpret the characters in the right way. It was tested with Contacs on Mac and Outlook

neograph734’s picture

Status: Active » Needs review

Thanks for thinking along. I had tried something similar earlier but for what I can recall it was not very successful. I'll try to test the patch in a few days.

neograph734’s picture

Status: Needs review » Needs work

So much for a reply in a few days... I totally forgot about this one.

Unfortunately this does not solve the problem for Windows contacts and Outlook 2016 (windows).

zekvyrin’s picture

Status: Needs work » Needs review

I don't know about windows, but on a mac the patch fixed the issue.

Can you re-checked it again on windows? (since it's a very old issue)

  • Neograph734 committed adb9c0e on 8.x-2.x authored by sludwig
    Issue #2866862 by sludwig: Windows contacts incorrectly displays special...
neograph734’s picture

Status: Needs review » Fixed

Tested and pushed to -dev. Thanks Zekvyrin for making me aware of this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.