> KUrl doesn't do any parsing. It uses QUrl for parsing. Therefore, "parsing > problems in QUrl" cannot be true, as it would be KUrl parsing problems too.
IIRC (haven't looke at kurl code in a while) it handled stuff like "../subd/" -> "", the escaped characters, local file uris and similar properly. I really consider that 'parsing'. > In my view, QUrl should be modified to use *only* partially-decoded components > and provide a method (toEncoded()) that returns the fully-encoded form for > proper network transfer. The partially-decoded form would decode %-encodings > that are UTF-8 sequences, including %20 to space, but not including delimiter > characterrs (so it won't decode %3F to a question mark in a path component, > but it would decode it in the query and fragment component). +1 -- Cheerio, Ivan -- While you were hanging yourself on someone else's words Dying to believe in what you heard I was staring straight into the shining sun _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
