"To repeat my question from yesterday: Why are you special-casing " and '? The spec doesn't say to do that. (And why are you converting " and ', but not (, ), *, +, etc?) Do you have any evidence that applications escape " or ' when sending notifications? If so, let me know, and I'll change the spec. If not, unescaped text will work more often without those conversions."
Because I removed the Pango markup parsing, which was doing this for us. Once I removed that then I would get IM's from friends that said things like, "Hey let's go see a movie" or whatever. I only added ', ', etc for thoroughness since you specifically mentioned doing that for ampersands, greater-than, and less-than characters. +#define CHARACTER_LT_REGEX "&(lt;|#60;|#x3C;)" This should be "&(lt;|#60;|#x3C;|#x3c;)" I'm doing caseless regex, so this isn't necessary. However, I'm not sure if < and < should be treated the same, so perhaps this is a bug and I should not be doing caseless? Let me know if that's wrong. I'll remove the <a href> regex stuff. It doesn't seem necessary now that the 'other' regex seems to be solid enough to pick those up now. -- Character reference handling for <, &, and > doesn't match notification-daemon https://bugs.launchpad.net/bugs/356659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
