-
-
Notifications
You must be signed in to change notification settings - Fork 46
Open
Labels
acceptedFeature or bug accepted. PR is welcome.Feature or bug accepted. PR is welcome.feature requestIssue is about a new feature or improving existing feature/behavior.Issue is about a new feature or improving existing feature/behavior.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
- I optionally donated to support the Fossify mission.
Feature description
Stock Android's Contact app represents the NICKNAME field in an idiosyncratic manner:
X-ANDROID-CUSTOM:vnd.android.cursor.item/nickname;Nick;1;;;;;;;;;;;;;
The request is to read this field properly by Fossify and then export it from Fossify in the standard manner, as:
NICKNAME:Nick
As a side note, Google Contacts does use the NICKNAME field properly.
Why do you want this feature?
If I create a contact in Stock, then I would like that to be read properly by Fossify.
Additional information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
acceptedFeature or bug accepted. PR is welcome.Feature or bug accepted. PR is welcome.feature requestIssue is about a new feature or improving existing feature/behavior.Issue is about a new feature or improving existing feature/behavior.