--Boundary-02=_1SLm90/vntwliX5
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Monday 30 September 2002 01:23, Ingo Kl=F6cker wrote:
<snip>
> the way we currently handle URLs in KMail is at best completely
> broken. Most of the time the mailto: URLs which we generate work
> correctly. But this is because we all have latin1-encodable names.
> The URLs break when the email addresses (or other URLs) contain
> characters which have a special meaning in URLs like '#' or '%'
> (http://bugs.kde.org/show_bug.cgi?id=3D47981). Furthermore they don't
> work at all with non-latin1-encoded names.
<snip>
> So we have to come up with a better solution for encoding arbitrary
> Unicode strings as URLs. Does anybody know which RFC deals with this
> and whether we already have a corresponding codec in kdelibs or
> whereever?

rfc 2368: The mailto URL scheme (proposed std; updates 1738)
rfc 2396: Uniform Rescource Identifiers (URI): Generic Syntax
(draft std)
rfc 1738: Uniform Resource Locators (URL) (proposed std).
rfc 1808: Relative Uniform Resource Locators (prop. std)
rfc 2141: URN syntax (proposed std)

rfc 2368:

2. Syntax of a mailto URL

   Following the syntax conventions of RFC 1738 [RFC1738], a "mailto"
   URL has the form:

     mailtoURL  =3D  "mailto:" [ to ] [ headers ]
     to         =3D  #mailbox
     headers    =3D  "?" header *( "&" header )
     header     =3D  hname "=3D" hvalue
     hname      =3D  *urlc
     hvalue     =3D  *urlc

   "#mailbox" is as specified in RFC 822 [RFC822]. This means that it
   consists of zero or more comma-separated mail addresses, possibly
   including "phrase" and "comment" components. Note that all URL
   reserved characters in "to" must be encoded: in particular,
   parentheses, commas, and the percent sign ("%"), which commonly occur
   in the "mailbox" syntax.

   "hname" and "hvalue" are encodings of an RFC 822 header name and
   value, respectively. As with "to", all URL reserved characters must
   be encoded.

   The special hname "body" indicates that the associated hvalue is the
   body of the message. The "body" hname should contain the content for
   the first text/plain body part of the message. The mailto URL is
   primarily intended for generation of short text messages that are
   actually the content of automatic processing (such as "subscribe"
   messages for mailing lists), not general MIME bodies.

   Within mailto URLs, the characters "?", "=3D", "&" are reserved.

   Because the "&" (ampersand) character is reserved in HTML, any mailto
   URL which contains an ampersand must be spelled differently in HTML
   than in other contexts.  A mailto URL which appears in an HTML
   document must use "&amp;" instead of "&".

   Also note that it is legal to specify both "to" and an "hname" whose
   value is "to". That is,

     mailto:addr1%2C%20addr2

     is equivalent to

     mailto:?to=3Daddr1%2C%20addr2

     is equivalent to

     mailto:addr1?to=3Daddr2

   8-bit characters in mailto URLs are forbidden. MIME encoded words (as
   defined in [RFC2047]) are permitted in header values, but not for any
   part of a "body" hname.



=2D-=20
Eternal vigilance is the price of liberty   -- Thomas Jefferson

--Boundary-02=_1SLm90/vntwliX5
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA9mLS13oWD+L2/6DgRAnojAKDoFkrdbMgL0KYFYqEOwCJy1l4tzACg2SnH
JsyXeBGvAHUq+AminH1kbTc=
=1tAf
-----END PGP SIGNATURE-----

--Boundary-02=_1SLm90/vntwliX5--

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail