Stumbling upon #506373 led me to find the root cause: my calendars are
were corrupt (from the point of view of utf-8 cleanliness) because of
the fact that Evolution processes correctly the various MIME parts that
make up a foreign invitation, EXCEPT the "charset" part. This is the
reason why the calendars ended up with a mixture of utf-8 and latin9.
The proper fix for this bug, of course, is to bleach again any entry
about to be copied. I suggest that each ticket gets validated from the
point of view of utf8ness, and if fails, the default encoding (as
applied in the mail view preferences) be attempted instead. Official
"unknown character" characters should be put in place if all fails, so
that the copy receives only valid utf-8 (as it should be).
Alternatively, another way of seeing the proper fix is to treat the copy
operation as a stricly GIGO operation, letting the correction of the
mess up to better times. Point is, there should NEVER be silent aborts
like currently.
-- Cyrille
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
