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

[David Faure]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 12 July 2002 02:46, Waldo Bastian wrote:
> In order to do it right, m_doc should know about the codec so that 
> m_doc->completeURL( url ) can do the right thing itself. Can I add that?

Fun. I remember adding a codec int to that method in the past, to fix
a similar problem, and then dropping this idea..... I can't remember why, though.
(I do think it's a correct fix though).

- -- 
David FAURE, david at mandrakesoft.com, faure at kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
KOffice-1.2-beta2 is out! http://dot.kde.org/1025176121/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9Lq5w72KcVAmwbhARAl42AJ0f9N5XKCXgVUGhvbfeZoldKaxRswCfacx0
Hvof+jPYrVnIgsYnJn7T/84=
=zaGv
-----END PGP SIGNATURE-----