Support Import of Apple & Google's vCard v.3.0 Extension, itemN.X-ABLabel
. Fossify Supports these as "Custom"
#187
Labels
feature request
Issue is about a new feature in the app
needs triage
Issue is not yet ready for PR authors to take up
Checklist
Feature description
Proposal to improve consistency of Fossify with other major vCard systems: Google, Apple, (and Nextcloud):
In vCard version 3.0 as exported from Apple or Google, there is an extension,
itemN.X-ABLabel
which are used to label entries in a contact. ie. a phone number might be labeled "Landline", an address might be labeled "POBox" and an email address might be labeled "Secondary". Neither the stock AOSP contacts app nor Fossify display or import these correctly, though custom labels are supported when a contact is created in the app. Stock labels these as "X-" while Fossify uses "TYPE=". So:Google (I understand it's the same for Apple):
Note that for Google, when the label is standard, eg. HOME or WORK, then it appears as:
Note that even this "standard" form of EMAIL is not imported/displayed correctly either by Stock or by Fossify, as the label ends up being interpreted as "Internet", not "Home". Also note that while Stock allows adding websites, Fossify does not.
When I export a contact created in the stock AOSP (GrapheneOS) contacts app, using the "custom" field for the label (other than websites, for which it is not available), it is rendered as:
When I export a contact created in Fossify, using the "custom" field for the label, that is rendered as:
Perhaps you'd be willing to modify Fossify to:
Read and display these Google/ Apple labels properly, and export them according to the vCard 4.0 TYPE= schema
Allow adding websites to a vCard, with custom labels. Note that the TYPE= schma is available in vCard 4.0 for URL. See the RFC.
This, along with a related ADR format issue should massively improve Fossify's consistency with other major vCard systems, including Nextcoud, Google, and Apple.
Thank you for a great app!
Why do you want this feature?
Compatibility.
Additional information
No response
The text was updated successfully, but these errors were encountered: