QUrl vs KURL - here's some benchmark results for you

[Thiago Macieira]

Waldo Bastian wrote:
>Websites provide URLs that consists of octets. Some of those octets may
> be %-encoded, some may not. It's important to preserve the exact octets
> as they appear in the page. However, as one of the first things, khtml
> converts all characters from 8-bit to a 16-bit QString, so if the
> octets where not %-encoded they may now have been changed as part of
> the toUnicode transformation. The KURL constructor tries to undo this
> transformation in the constructor and then %-encode all non-ascii
> characters.

That's something that IRI comes to change: the non-%-escaped characters 
are meant to be interpreted as Unicode codepoints, whatever encoding they 
were in.

So the KURL de-transformation should disappear.

-- 
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

3. Ac seo woruld wearð geborod, swá se Scieppend cweað "Gewurde Unix" and 
wundor fremede and him "Unix" genemned, þæt is se rihtendgesamnung.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050603/8deca74c/attachment.sig>