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

Read and Interpret Properly Stock Android's "Nickname" field. #194

Open
7 tasks done
DiagonalArg opened this issue Nov 29, 2024 · 0 comments
Open
7 tasks done

Read and Interpret Properly Stock Android's "Nickname" field. #194

DiagonalArg opened this issue Nov 29, 2024 · 0 comments
Labels
feature request Issue is about a new feature in the app

Comments

@DiagonalArg
Copy link

DiagonalArg commented Nov 29, 2024

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

@DiagonalArg DiagonalArg added feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Nov 29, 2024
@Aga-C Aga-C removed the needs triage Issue is not yet ready for PR authors to take up label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue is about a new feature in the app
Projects
None yet
Development

No branches or pull requests

2 participants