Internationalization (i18n) Activity

Making the World Wide Web worldwide!


Group pages

i18n Working Group

MultilingualWeb-LT Working Group

i18n Interest Group

Internationalization Tag Set (ITS) Interest Group

Indic Layout Task Force

Japanese Layout Task Force

Activity Statement

W3C Validator Suite
Includes i18n Checker

Site links

Getting Started
Tasks
Topics
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Resource types
Reviews
Mail archives
Aggregated data
Translation
News by category
News archives
July 2011 (13)
July 2009 (10)
June 2009 (10)
June 2008 (13)

Search for news

Admin

Updated article: An Introduction to Multilingual Web Addresses

Read the article

Information was updated about support for paths as IRIs in latest browsers. For a detailed list of changes read the full post.

The following text was changed: [[

The conversion process for parts of the IRI relating to the path is already supported natively in the latest versions of Opera and Safari. It works in Internet Explorer 6 if the option in Tools>Internet Options>Advanced>Always send URLs as UTF-8 is turned on. This means that links in HTML, or addresses typed into the browser's address bar will be correctly converted in those user agents.

It doesn't work out of the box as of January 2005 in Mozilla, Netscape or Firefox (although you may obtain results if the IRI and the resource name are in the same encoding). Technically-aware users can turn on an option (set network.standard-url.encode-utf8 to true in about:config) to support this, but it is not yet exposed in the user interface. There are indications that it may be supported by default in Firefox 3.

]] to [[

The conversion process for parts of the IRI relating to the path is already supported natively in the latest versions of IE7, Firefox, Opera, Safari and Google Chrome.

It works in Internet Explorer 6 if the option in Tools>Internet Options>Advanced>Always send URLs as UTF-8 is turned on. This means that links in HTML, or addresses typed into the browser's address bar will be correctly converted in those user agents. It doesn't work out of the box for Firefox 2 (although you may obtain results if the IRI and the resource name are in the same encoding), but technically-aware users can turn on an option to support this (set network.standard-url.encode-utf8 to true in about:config).

]]

Categories: Update

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Before you comment here, note that your IP address is sent to Akismet, the plugin we use to mitigate spam comments.


Copyright © 2014 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.
Questions or comments? ishida@w3.org