flexibeast
commented
10 years ago The problem isn't that the values of the fields are in UTF-8; the problem is the presence of the CHARSET property modifier. The canonicalisation process currently doesn't remove that, leaving a property "N;CHARSET=UTF-8" that doesn't exist in any mappings, thus causing it to get skipped. You can verify this for yourself by removing ";CHARSET=UTF-8" from any line that has it, then running org-vcard-import on the result.
At this point i want to focus on supporting only UTF-8 and ASCII - vCard 4.0 mandates UTF-8 overall, vCard 2.1 mandates ASCII overall, and i'm not yet clear whether vCard 3.0 mandates an encoding or not. In terms of importing, a quick hack that might work would be to discard modifiers like CHARSET=UTF-8; but in terms of exporting to vCard 2.1, output is currently encoded as ASCII (as per the standard), but obviously being able to specify and output a non-ASCII CHARSET for individual properties is critical.
So, thanks for bringing this to my attention - i'll have to give some thought to how to handle and fix it.
Finally, as with many other interactive commands, you can get a list of possible completions by pressing TAB at each prompt. i will certainly update the documentation to note this!
sg2002
Hello. This project has great potential, but in the current state it's unusable for me, because of a couple of issues. The first is unicode support. It seems that if a property is declared as having a charset, it's just skipped. Here's an example vcard:
BEGIN:VCARD VERSION:2.1 N;CHARSET=UTF-8:Пупкин;Василий TEL;HOME:+74951234568 TEL;WORK:+74951234569 TEL;FAX:+74951234560 TEL;CELL:+74951234567 TEL:+74951234561 ADR;HOME;CHARSET=UTF-8:;;Кремль;;;; END:VCARD
Since both address and name fields are in unicode, they do not appear in the conversion output.
Also, some interactive hints would be nice, I had to look into the source code to understand what should be entered in Source and Destination fields during the import.