Sebastian Rose wrote:
>Is there a reason for this distinction between multibyte and unibyte?
>I favour the "shotgun-approach" if not.  It's bullet-proof.

>The JavaScript function `encodeURIComponent()' encodes the German Umlaut
>`ü' as `%C3%B6' regardless of the sources encoding actually.  That's why
>I wrote the two functions `org-protocol-unhex-string' and
>`org-protocol-unhex-compound' (s. org-protocol.el).

Ah, yes.  From my understandig of the RFC %C3%BC is a valid
representation of the "ü" character.  

I do not yet fully understand
how to unescape such a representation.  E.g. Is %C3%BC a hexencoded
multibyte char or a succession of two singlebyte chars?

>I'll have to take a look at that RFC you mentioned :)

Me too :D

Best,
  -- David
-- 
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de