RE: URL encoding used by Safari for non-ascii chars ??
RE: URL encoding used by Safari for non-ascii chars ??
- Subject: RE: URL encoding used by Safari for non-ascii chars ??
- From: "Sanjay Arora" <email@hidden>
- Date: Sat, 8 Jan 2005 17:56:21 +0530
- Thread-topic: URL encoding used by Safari for non-ascii chars ??
Thanks Alexey,
Is there a way I can distinguish between UTF-8 stream and the decomposed UTF-8 stream.
As Safari is sending both kinds of streams to my server.
Regards
Sanjay
-----Original Message-----
From: Alexey Proskuryakov [mailto:email@hidden]
Sent: Thursday, January 06, 2005 2:21 AM
To: Sanjay Arora; email@hidden
Subject: Re: URL encoding used by Safari for non-ascii chars ??
On Thu, 6 Jan 2005 00:22:44 +0530 "Sanjay Arora" <email@hidden> wrote:
> An example for a Central European character (ä). e.g. http://server/ä
>
> ä = ä --> 195 164 (UTF-8) --- (When I type the char in the address
>window)
>
> ä = ä --> 97 204 136 (??) -- (When I type copy and paste the char in
>the address window)
The second encoding is also UTF-8, but for a different (decomposed) form of
Unicode. In UTF-16, the same would be U+0061 U+0308. U+0061 is 'a', and U+0308 (776 in dec.)
is a combining umlaut, ̈. You may want to spend some time with a freeware
utility UnicodeChecker (http://earthlingsoft.net) - IMO it's the best way to
get acquainted with the basics of Unicode.
A good HTTP/WebDAV server should accept any form of Unicode, of course.
- WBR, Alexey Proskuryakov
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden