On Fri, 2012-09-07 at 15:22 +0200, Ove Kåven wrote:
On 09/07/2012 09:34 AM, Patrick Ohly wrote:
> The problem is that if the peer doesn't know about it and just changes
> 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
And if they were under time pressure or wanted to avoid expensive
runtime checks, they might have decided instead to not implement this
and instead demand that the entity writing the item does the right
But further testing may be needed to find out if that actually
Yes, please test.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.