QR-Code Generator Problems with Umlauts in vCards

Unfortunately I still have the same issue 🤔 🤔 (InDesign version 20.0.1)

Ja, Adobe hat mit der neuen Version von Indesign die Umlautefehler behoben und die VCARD-Version auf 3.0 erhöht. Jedoch sind immer noch nicht mehr Eingabefelder hinzugekommen. Ich habe ein Skript geschrieben, welche die Anzahl der VCARD-Felder massiv erhöht, die Werte ganz einfach eingegeben, beziehungsweise geändert werden können inklusive die Farben. Siehe hier https://steigart.ch/qr-code-mit-umlaute-fehler-in-indesign/

Die Seite und das Skript sind zwar auf Deutsch, doch sollte das kein Problem sein. Falls doch kannst Du mir das sagen, dass schreibe ich das Skript um.

Yes —

• Don't use the fixed vCard form, which is locked at the obsolete version 2.1;
• Use Plain Text for, well, pretty much everything.

This advice is given throughout the recent answers to most QR code topics here. Including above, in this one. 🙂

There will always be a need for solutions until Adobe updates this feature/applet, either defaulting to v3.0 or allowing an evident selection of the vCard version. The problem, though, is that many designer/users simply don't know about QR code/vCard versions and this limitation of the v2.1 standard, so having their codes fail when upper ASCII characters are used is just a mysterious glitch.

You might edit your post to describe what your solution is, to better guide future visitors.

I tried this.

My QR-Code App do not recognize this as a vcard.

What or how are you importing the codes? Are you using some third-party app or generator? Or using InDesign's 'Plain Text' mode to generate them?

And when you say "edit them in ID" — do you mean editing in the same plain text mode, or opening the vCard form and editing values there?

If the latter — there's no differnence, I believe, between creating them using the limited (v2.1) vCard form, and editing them once created; I suspect if you examine the raw code in the result, it will be either reset to v2.1 or othewise corrupted.

QR code data is almost always plain text, with a "FIELDNAME:fielddata" format. In theory, you could add a (vCard or BizCard) field with any combination of content you like, for any social media or communication channel.

Whether it would work or not, though, depends (a little, if any) on the QR code reader and how it parses the content but mostly on the destination app — if your device's "Contact" app or equivalent doesn't know what to do with a WECHAT or DISCORD or SLACK data field, it will most likely just ignore/discard it, or assign it to a text field.

Making any such extension work would have to start with seeing if the Contact app has any protocol for accepting and filing that address information, then following it with the correct field name and any peculiarities of encoding the field value.

There is no "problem," exactly, except that all the form-driven code creation is a bit simplified, and Adobe is chosing to use v2.1 encoding as the default. Using the plain text method, with a fuller understanding of not just vCard structure but all the other alternatives, makes the ID encoder a valuable asset, since it is secure and standalone.

QR-Code als Text funktioniert leider nicht zuverlässig mit manchen QR-Readern auf Android-Smartphones.

Was das ganze Problem beheben würde, wäre, wenn InDesign Version 4.x vCards generieren würde. Denn diese lassen nur noch utf-8 als Kodierung zu. Ich weiß nicht, warum InDesign gerade in diesem Punkt so Rückständig ist. Das Problem ist ja schon an anderen Stellen im Forum diskutiert worden, und das letzte mal vor ca. 2 Jahren als bug gemeldet worden. Möglicherweise ist der nicht-englischsprachige Markt für Adobe vernachlässigbar klein??

hey there. Unfortunately I don´t get it. can you please tell me where to put which text in order to get working QR vcards with "Umlaute". thx