New issue 1017 by deba...@debian.org: Postal address in vCard not parsed
correctly
http://code.google.com/p/zxing/issues/detail?id=1017
What steps will reproduce the problem?
1. use a vCard with the address line "ADR;WORK:;10 Downing
Street;London;;SW1A 2AA;UK"
2. create a QR code from it, e.g. cat vCard | qrencode -o qr.png
3. scan it with zxing
What is the expected output? What do you see instead?
I expect, that after adding the contact, the address is added to "work
address", cleanly separated into street, postal code etc.
Instead, the address is interpreted as "home address", and street, postal
code etc. are not separated at all.
What version of the product are you using? On what operating system?
3.6 on Android 2.3.3 (Samsung Galaxy S I9000)
Comment #1 on issue 1017 by sro...@gmail.com: Postal address in vCard not
parsed correctly
http://code.google.com/p/zxing/issues/detail?id=1017
This is not a parsing problem, but an Android contacts API limitation.
Actually, wait a moment -- it should be able to assign to home/work
correctly. That's a recent change though; try the SVN version. It is
possible in Android 1.x; the rest is not.
Many thanks for your quick answer! Well, the home/work thing is not too
important, as you can change this in the Contacts program easily.
Cut-n-pasting street, city, postal code is more annoying.
I wonder how the Contacts GUI is able to distinguish between street, city,
and postal code, if it's not in the API? Do they use some non-API
functions? Just curious...
It's the Contacts app doing that logic, not the underlying Intent-based
API. I think it is able to store and retrieve these as individual fields
since it's accessing its own representation directly as a ContentProvider.
I think it's possible to access that, though ties you a lot more directly
into one app and its implementation. We're sticking with Intents for now.