[Vobject] vCard 2.1 behaviour

martin f krafft madduck at madduck.net
Thu Oct 25 02:40:25 CDT 2012


Hello,

consumer devices that support vCard hardly ever can deal with
versions 3.0 or 4.0, but are limited to 2.1 — it's almost like
programmers at phone manufacturers and other places have access to
a snapshot of the Internet from 1997 and use that as authoritative
reference… :(

Unfortunately, your lovely vobject module does not come with
a vCard2_1 behaviour. That's probably because most of you have
little interest in coding historical stuff.

Yet, given the ubiquity of vCard 2.1, I do wonder whether
a vCard2_1 would make sense…

I had a look at vcard.py and it doesn't look like it'll be that hard
to do. Essentially, starting from a copy of the VCard3_0 class, all
that seems necessary is to change some class variables, provide
encode/decode (since 2.1 uses whack/ancient encoding), and possibly
change the knownChildren attribute.

Have any ventures into this domain already taken place?
Are you interested in a VCard2_1 behaviour?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"i believe that the moment is near when by a procedure
 of active paranoiac thought, it will be possible
 to systematise confusion and contribute to
 the total discrediting of the world of reality."
                                                      -- salvador dali
 
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 1124 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: <http://lists.skyhouseconsulting.com/pipermail/vobject/attachments/20121025/ea31a30d/attachment.pgp>


More information about the VObject mailing list