Version: 4.6 beta5 (using KDE 4.6.2) OS: Linux I run a kolab server version 2.4, and have been using KDE3 kontact for a long time. Recently I experimented with the upcoming akonadi-based kontact, which seems to be working fine on linux, except for one issue: Notes created with the knotes component in KDE3/older KDE4 clients on the kolab server are displayed as raw rich text without applying the formatting - lists get almost unreadable due to the large number of tags. Vice versa, notes created with the new kjots component and stored on the kolab server do not display at all in older KDE3 or KDE4 clients based on knotes. Reproducible: Always Steps to Reproduce: a) Set up kolab server. Create note in KDE3 Kontact with knotes on it, using rich text format. Use KDE4 kontact to read it. b) Set up kolab server. Create note in recent KDE4 client using kjots component on the server. Use KDE3 Kontact or older KDE4 version using knotes component to read the notes. Actual Results: a) Displays raw rich text. b) The note created earlier does not appear at all. Expected Results: a) Contents of note should be displayed with correct formatting applied. b) Note should appear, it should be able to read/modify it with knotes.
Still not working with KDE 4.7.2.
Here the error of showing raw text instead of formatted text also appears when the note was created by kjots. When closing kontact and starting a new instance a formatted text is displayed as raw text. Bye Thorsten -- kde4-config --version Qt: 4.7.4 KDE: 4.7.97 (4.8 RC2 (4.7.97) kde4-config: 1.0 dpkg -l |grep kjots kjots 4:4.7.97-0ubuntu1~oneiric1~ppa1 note-taking utility Kolab2-Groupware-Server-Version 2.2.4
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.