https://bugs.kde.org/show_bug.cgi?id=342369
--- Comment #12 from Daniel Vrátil <[email protected]> --- The problem is that if we keep some data only locally because we cannot sync them to Google, it goes against the principle of Akonadi being only a cache and it can also lead to data loss - if you would delete your Akonadi database, you would lose all this information that we couldn't upload to Google. We should encode the custom fields that Google does not support out-of-the-box into some "extra" fields that we can sync to Google (but unfortunately no other clients will likely be able to understand them), and eventually have the feature where the Contact Editor would only allow changing fields that the respective backend supports (so if Google does not support Contact name ordering, we would simply not make it configurable when creating a new contact in Google Contacts addressbook). For now, I'll look into the first step - encoding everything into the extra fields. -- You are receiving this mail because: You are on the CC list for the bug.
