-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Feature request] Add support for structured addresses #30
Comments
It would be great if @stephanritscher's patches could be merged into Fossify Contacts. I’ve been using his fork for a while and it works very well. Not only does it implement the correct address separation the vCard standard requires, Right now Fossify Contacts, same as the main-line Simple Contacts before it, stores the complete address in the street address field, which is just wrong; so I wouldn’t even consider this a feature request but a bug ticket. Update: Since I’ve made the mistake of assuming the formatting feature mentioned above, I’ve made a corresponding feature request at stephanritscher/Simple-Contacts#18. Should proper address handling find its way into Fossify Contacts, the same would be nice to have here as well. |
For context, here is the original Simple Contacts discussion of this issue: Apparently the developer @tibbi thought making the address format standards-compliant was too much of a “complication.” |
Must needed as now a days many people have structured addresses in Google Contacts. Import will be not proper without it. |
Checklist
Is your feature request related to a problem? Please describe.
At the moment there is only a single field for addresses. Therefore addresses are not synced correctly when also syncing with other clients like Thunderbird which have structured address field support.
Describe the solution you'd like
Add individual fields for the different address parts. Could be done as an option to support simple mode also for people who preferre this.
Describe alternatives you've considered
The different fields could be merged into one during sync. This would not improve editing behavior.
Additional context
This fork of Simple Contacts already contains structured address fields and I think the author would be willing to contribute.
https://github.com/stephanritscher/Simple-Contacts
The text was updated successfully, but these errors were encountered: