On 09/07/2012 09:34 AM, Patrick Ohly wrote:
The problem is that if the peer doesn't know about it and just
the plain text description, then DESCRIPTION and X-ALT-DESC will become
Therefore preserving X-ALT-DESC locally must become more intelligent
than "always preserve it". It needs to know whether the peer really
supported the X-ALT-DESC and updated it together with the DESCRIPTION
and if not, needs to check whether the DESCRIPTION was modified.
Well, not necessarily. The Harmattan designers would probably have
foreseen such issues. If I was a Harmattan software engineer and coaxed
into adding support for HTML descriptions in the calendar/notes, what I
would do was to have the calendar UI first try to load the X-ALT-DESC
(if it exists), convert it to plaintext, and compare that with the
DESCRIPTION. If it's different, the UI would then know that the two are
out of sync, and I would then have the UI ignore/discard the X-ALT-DESC
version, and just load the DESCRIPTION text, assuming some
non-HTML-aware system changed it without changing the HTML version.
If the UI does that, then there may not be much need to add a lot of
logic for keeping these in sync. The Harmattan UI would show the correct
version in any case.
But further testing may be needed to find out if that actually happens,