I guess the best thing would be to find the faulty note. I know it's tedious, but the problem was with HTML generated from the web editor that was completely wrong. This is now fixed, and we don't crash anymore on wrong HTML/XML, but there's nothing we can really do about your corrupted note.
Some tips though:
* the note was probably saved with the web editor before the fixes, so you probably haven't edited it for a long time
* now for broken HTML/XML, we just escape all tags and display that, so if you haven't seen weird notes' contents on either Tomboy or the web UI, it's probably a note you don't use too often. So, I would just suggest you leave it as it is, and when you see it, you just fix it editing it on the web UI or Tomboy.
Of course, as I said, we shouldn't be crashing on the web UI, so if you see that, please reopen the bug
I guess the best thing would be to find the faulty note. I know it's tedious, but the problem was with HTML generated from the web editor that was completely wrong. This is now fixed, and we don't crash anymore on wrong HTML/XML, but there's nothing we can really do about your corrupted note.
Some tips though:
* the note was probably saved with the web editor before the fixes, so you probably haven't edited it for a long time
* now for broken HTML/XML, we just escape all tags and display that, so if you haven't seen weird notes' contents on either Tomboy or the web UI, it's probably a note you don't use too often. So, I would just suggest you leave it as it is, and when you see it, you just fix it editing it on the web UI or Tomboy.
Of course, as I said, we shouldn't be crashing on the web UI, so if you see that, please reopen the bug