--nextPart1333451.VkVAmEyMtd
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Michael Pyne wrote:
>The theory's all well and good guys, but if people are using a URL, it's
>because they don't *need* a URI, which generally means they're not doing
>URI-like things to it.  If programs are trying to turn URLs into URIs in
> a class that doesn't design it, they're buggy.

I'm sorry, but reality proves you wrong. People ARE using URIs, even if=20
they don't know they are.

The prime example are mailto: URIs. They are not URLs, yet everyone=20
expects them to work with KURL and QUrl.

If you try to tell people "you can use ONLY URLs with this class and for=20
the rest you must use QString", you'll get problems.

Whatever KDE4 uses for KURL's replacement, it must handle mailto:=20
(including ToASCII on the domain part), and ed2k. What Qt will never do=20
is read .protocol files, like KURL does. A compromise has to be found.

I, for one, wouldn't miss ed2k if it were completely dumped and regarded=20
as invalid (because it is). Users would not agree with me, nor would many=20
developers.

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

5. Swa he g=C3=A9anhwearf t=C3=B3 timbran, and hwonne he c=C3=B3m, l=C3=A1!=
 Unix cw=C3=A6=C3=B0 "Hello,=20
World". =C7=BCfre =C7=BDghwilc w=C3=A6s gl=C3=A6d and seo woruld w=C3=A6s f=
r=C3=A9o.

--nextPart1333451.VkVAmEyMtd
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCjXDJM/XwBW70U1gRAotDAKDHgClmNYiysSBZA+1EEkVn7dVfVgCgwgSK
4Hmg7NfoSWhz9IDD2eOmEUk=
=qFnJ
-----END PGP SIGNATURE-----

--nextPart1333451.VkVAmEyMtd--