W3C home > Mailing lists > Public > www-international@w3.org > January to March 2000

Re: Prediction for non-ASCII URLs

From: Suzanne Topping <stopping@rochester.rr.com>
Date: Mon, 10 Jan 2000 16:20:28 -0500
Message-ID: <017701bf5bb0$878252e0$40c25f18@rochester.rr.com>
To: "www" <www-international@w3.org>
Thanks for this response Roozbeh.

Pardon my ignorance on this subject, but can you tell me how this ends up
impacting the user? Is it transparent? For example, if a user enters a URL
which includes Japanese characters, does the browser display the converted
URL in the address it displays from then on? Or is this converting and
encoding handled behind the scenes, and the display remains in Japanese?

My point is that if the display is converted straight away, then the user
impact is still pretty significant. Lets say that they enter the
Japanese-friendly URL, which gets immediately converted and displayed using
the % encoding, and then they go down a few levels and want to capture what
the new URL is. If the display now contains the whole huge string of
converted characters, the user is stuck with an unwieldy URL.

But perhaps this is a processing issue rather than a display issue.

Thanks again for any help you can give me in understanding how this is
handled.

Suzanne Topping
Localization Unlimited

----- Original Message -----
From: Roozbeh Pournader <roozbeh@sina.sharif.ac.ir>

Internet Explorer 5 already uses that for default. If you use any
non-ASCII characters in the URL, it will convert it to UTF-8 and %-encode
it. Perhaps Microsoft Internet Information Server also does that.
Received on Monday, 10 January 2000 16:24:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:55 GMT