You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With DAVx5/4.2.3.4-ose (as installed through F-Droid, used on LineageOS 14.1) I've observed that property parameters present in the original vCalendar or vCard file are not present after the file was modified through DAVx5.
These concrete parameters may not be particularly valuable, but I'd have a hard time figuring out the precise conditions on which parameters are affected, and generally these should be preserved.
Is this a known issue, could it be fixed easily, and if so, where?
I've considered whether the server could assist in working around this (I'm using radicale 3.1.8 as a server, but that should not matter), but it simply does not have enough information to distinguish between a client removing a parameter intentionally and removing it because it does not know it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With DAVx5/4.2.3.4-ose (as installed through F-Droid, used on LineageOS 14.1) I've observed that property parameters present in the original vCalendar or vCard file are not present after the file was modified through DAVx5.
Concrete examples are
in vCard files, and
in vCalendar files.
This appears to only affect properties that are recognized by DAVx5 -- lines such as
are unaffected.
These concrete parameters may not be particularly valuable, but I'd have a hard time figuring out the precise conditions on which parameters are affected, and generally these should be preserved.
Is this a known issue, could it be fixed easily, and if so, where?
I've considered whether the server could assist in working around this (I'm using radicale 3.1.8 as a server, but that should not matter), but it simply does not have enough information to distinguish between a client removing a parameter intentionally and removing it because it does not know it.
Beta Was this translation helpful? Give feedback.
All reactions