Created attachment 204503 [details] example vCard file Currently the QR dialog is able to create a QR code from data describing a textual vCard file (see attachment). However it is not easy to manually create such a dataset, and it would be convenient to add an extra dialog to provide some optional contact info (several optional fields: N ; ORG ; TITLE ; TEL; EMAIL; ADR; URL ) to be saved as QR code, containing a vCard.
STR: Copy the content from the vCard file, paste into the URL/Text field, and generate the QR code. (We might need to find a better name for the text field.) -- The RFC lists a lot of properties additionally to what you shared in the example with BEGIN:VCARD N:Nachname;Vorname ORG:Unternehmen TITLE:Funktion / Berufsbezeichnung TEL;TYPE=WORK,VOICE: Telefonnummer EMAIL;TYPE=WORK: E-Mail-Adresse ADR;TYPE=WORK:;;Straße und Hausnummer;Stadt;Bundesland;PLZ;Land URL:Website-URL END:VCARD I suggest to have an extra dialog started via "Import from vCard". This dialog could show the most important items as individual fields and the extra points per dropdown preselection. Similar to how we handle the document properties (or rather how it was for a while). The dialog could also have import/export buttons to manage vCard files. Alternatively, we may show URL/Text/vCard as tabs and make the input box depending on the selection. It would be either a one line input, the current box, or a structured list of edit fields for vCard.
+1, but I imagine we'd want/need to fully parse against the IETC RFC 6350 for vCode and try to maintain that compliance. It would result in a more complex/higher error check QR Code format (likely mostly empty) but would be of greatest use to folks adopting. And we might be able to add a center image--e.g. vCard by LibreOffice And guess our ZXing based implementation could support alternate 2D data matrix format(s) if users had requirement, e.g. Aztec Code or MaxiCode, rather than QR Code.