[Vobject] vCard 2.1 behaviour

[Adam Tauno Williams]

On Thu, 2012-10-25 at 09:40 +0200, martin f krafft wrote:
> 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…

Yes, please, implement this.  I'm facing this right now! :)

> 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?

It has been mentioned a few times in the past.