From kde-core-devel  Mon Mar 13 18:32:35 2000
From: Yves Arrouye <yves () realnames ! com>
Date: Mon, 13 Mar 2000 18:32:35 +0000
To: kde-core-devel
Subject: RE: KURL encoding question
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=95297440311890

If we say that everything should be properly encoded before it's given to
KURL (something I heartily agree with), it does mean that we want to change
a number of applications that don't do it, right? For example, Konqueror
builds URLs directly from user's input (and then konq_searcher gets it as
straight Unicode, and will encode it for URL later), or do things like:

	openURL(0L, KURL(QDir::homeDirPath().prepend("file:")));

My understanding here is that QDir::homeDirPath() can be in any charset,
depending on the user settings, so I wonder 1/ how to cope with that
correctly, and 2/ shouldn't KURL::encode(QDir::homeDirPath()) be used
instead? I believe many applications using URLs must be doing this, no (I
just picked Konqueror because that's the one I'm the most familiar with, and
could fix easily)?

Another question is: do we guarantee/require that the decoded URL is UTF-8?
That would be very convenient to write generic code, but will certainly
require changes when one builds a URL from a filename. What will happen
here? How do you distinguish between Japanese/Arabic/Russian/etc...
filesystems?

YA.