Version: unknown (using 4.00.61 (KDE 4.0.61 >= 20080207), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.24-git4 Hi, this is highly debatable but while the file:// scheme might be correct to use internally, imho those file:///foo/bar urls look confusing and unpleasant with those triple slashes. As the URL parses just fine without the file:// which is obviously the prerequisite for an URL returned by prettyUrl it should not break anything. There is a piece of leftover code in kurl.cpp which seems to have done just that. Why was it left there if not with the intent to make prettyUrl strip file:// part again? David, clues, suggestions? Opinions?
The behavior that you want is given by pathOrUrl().