it is a bug, but it is rather complicated due to missing support for UTF-8 surrogates in
When it will be ready I will send you a patch.
On 3 Nov 2016, at 13:35, Pander
Is there any progress on this bug? This limits our use of Caldavzap a
lot. Willing to test any patches.
On 2016-10-16 15:54, Pander wrote:
With other calendar clients this works but not with caldavzap. When I
enter a Unicode character with a high code point, it is not saved. For
example U+1F511 🔑 (symbol for a key) is not saved. It is shown when
added in an vevent by another client.
Is this reproducible and can this be fixed?