[kontact] [Bug 342387] the phones type should be customizable

2023-05-05 Thread VINCENT
https://bugs.kde.org/show_bug.cgi?id=342387

VINCENT  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---

--- Comment #6 from VINCENT  ---
With the update of KDE Gear in 23.04, i did hope that there will be some
rebuild on this subject, but importing vcard still don't work as expected,
since there is some missing information.
Not supporting the "X-ABLABEL" lead to lost of data when importing vcard, and
may lead to lost of data on various contact server if kde contact upload it's
own version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 342387] the phones type should be customizable

2023-05-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=342387

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 342387] the phones type should be customizable

2023-04-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=342387

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 342387] the phones type should be customizable

2023-04-05 Thread VINCENT
https://bugs.kde.org/show_bug.cgi?id=342387

VINCENT  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |NOT A BUG
 CC||stphane.vinc...@gmail.com

--- Comment #3 from VINCENT  ---
This functionality is already available in
nextcloud/google/cardbook(thunderbird). Could this be implemented ?

It's based on the support of "X-ABLABEL" in vcf files. and is concerning a
bunch of fields (EMAIL, TEL, ADR, URL, X-ABDATE)

Some example :
ITEM1.EMAIL:mail_...@gmail.com
ITEM1.X-ABLABEL:Pro
ITEM2.TEL:+33 6 12 34 56 78
ITEM2.X-ABLABEL:Mobile (pro)
ITEM3.X-ABDATE:19700805
ITEM3.X-ABLABEL:Année

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 342387] the phones type should be customizable

2018-05-28 Thread alberto
https://bugs.kde.org/show_bug.cgi?id=342387

alberto  changed:

   What|Removed |Added

 CC||paj...@gmail.com

--- Comment #2 from alberto  ---
This is not only wish list, its kinda needed too

If kontact is supposed to be able to interact with other programs. Any other
programs allow custom tags for phones. After syncing with kontact using webdav,
kontact silently dropped everything it didnt understood and making some changes
to the contatc, it updated the remote vcards dropping everything it didnt
understood

Including custom tags that radical/evolution/gmail were able to show and to
transfer between them perfectly

Luckily i run the backend where i save the vcards in git and i was able to
detect the mess quite fast. Im not sure I want to touch kontact again looking
at this policy with unknown data. Its bad enough that is not able to show it
properly, but to erase it?

Just add everything you dont understand to notes or something

The severity of this bug should be higher than wishlist imho. In other notes,
Should I open a bug about the data lost using webdav or is this bug enough?

-- 
You are receiving this mail because:
You are watching all bug changes.