how Windows browsers encode URL [Re: why the % cruft?]

[Waldo Bastian]

On Friday 12 July 2002 03:37 am, Lars Knoll wrote:
> So putting a Unicode URL into KURL, then setting the encoding to latin1,
> and afterwards to eg. utf8 should not result in any operation that looses
> data.

I fail to see why it is so hard to set the encoding right the first time. You 
don't read HTML pages as "latin1" first and then later change the QStrings to 
correct for the fact that the encoding should have been utf8, do you?

If you set the wrong encoding then KURL::url() will return the wrong result. 
If you continue to work with those wrong results then things will not 
automagically correct themselves after you throw them into a KURL with 
another encoding set.

Cheers,
Waldo
-- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com