On Thursday 19 January 2012 15:16:29 Robin Burchell wrote: > Hi, > > On Thu, Jan 19, 2012 at 11:02 AM, <lars.kn...@nokia.com> wrote: > > Is there really any big value in having this? It feels wrong to have > > special handling for HTML in here. While it's one of the most prominent > > formats for rich text, there are so many other formats that would require > > different escaping and we certainly don't want to support them all. I can > > live with toHTMLEscaped(), since it cleans up a really messy part of the > > Qt 4 API, but I'm not sure I want to extend this a whole lot more. > > Big value, well... as you mentioned, it's common. I've needed to write > code to do entity decoding in the past, I'm sure a lot of others have.
Yep. http://lxr.kde.org/ident?i=resolveEntities shows 6 different KDE apps which have a need for it. Plus one using fromEntity. IMHO this shows that this functionality should really be in Qt indeed (but not necessarily in QString or even in QtCore) -- David Faure | david.fa...@kdab.com | KDE/Qt Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development