Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MECARD / vCard encoding should delimit fields #23

Open
srowen opened this issue Jan 18, 2014 · 3 comments
Open

MECARD / vCard encoding should delimit fields #23

srowen opened this issue Jan 18, 2014 · 3 comments
Labels

Comments

@srowen
Copy link
Contributor

srowen commented Jan 18, 2014

Address / city / state / postal code and so on are supposed to be separated in MECARD and vCard, by comma and semicolon, respectively. The code right now doesn't break this down beyond an address field though, so isn't able to format accordingly.

Ideally the online encoder would have separate fields for address components. And, in Android, would retrieve address elements independently. However I am not sure Android breaks this out either, not via Intent.

Ported from https://code.google.com/p/zxing/issues/detail?id=1468

@rotdrop
Copy link

rotdrop commented Sep 9, 2015

Hi, this still does not work, i.e. the individual address fields are still merged into the "street address" when importing into the contacts app on Android (SGS3 with Android 4.3). OTOH, when I download a vCard file and import it with the import functionality of the contacts app, "everything" seems to work correctly. Is there a known work-around, like storing the decoded data as a .vcf file on the sd-card? I know I can somehow export the history as CVS file etc. but there does not seem to be an obvious way to simply store the data in the file-system, for later import by other apps. Thanks,

Claus

@srowen
Copy link
Contributor Author

srowen commented Sep 9, 2015

That's not quite what this issue is about. You're talking about behavior of the Contacts app. This is about delimiting address elements, which may or may not change Contacts behavior. It's open because indeed it is not resolved. You are welcome to work on it.

@Ayyan551

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants