Tag(s): article-idn-and-iri

Ukrainian:

Використання <select> для Посилання на Локалізований Контент (Using <select> to Link to Localized Content)

Запровадження Багатомовної Веб Адреси (An Introduction to Multilingual Web Addresses)

Налаштування відображення мови за допомогою Apache MultiViews (Apache MultiViews language negotiation set up)

Особисті імена в різних мовах світу (Personal names around the world)

Russian:

Использование <select> для Ссылания на Локализованный Контент (Using <select> to Link to Localized Content)

Введение Многоязычного Веб Адреса (An Introduction to Multilingual Web Addresses)

Настройка отображения языка с помощью Apache MultiViews (Apache MultiViews language negotiation set up)

Личные имена в разных языках мира (Personal names around the world)

These articles were translated thanks to Alexandr Shlapak.

Controlere Unicode vs. marcare pentru sprijinul bidi (Unicode controls vs. markup for bidi support)

Dimensiunea textului in traduceri (Text size in translation)

O introducere in Adresele Web Multilingve (An Introduction to Multilingual Web Addresses)

These articles were translated into Romanian thanks to Costea Marian.

Ejecución de HTML & XHTML (Serving HTML & XHTML)

Introducción a direcciones web plurilingües (An Introduction to Multilingual Web Addresses)

Formatos de fechas (Date formats)

Capacidades de visualización (Display capabilities)

These articles were translated into Spanish thanks to the Spanish Translation Team, Spanish Translation US.

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).

]]

A paragraph about Firefox support for IRIs was updated. For a detailed list of changes read the full post.
Prompted by Jarl Friis, I changed the following paragraph:
“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 to support this, but it is not yet exposed in the user interface.”
to read:
“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.”

Translators should consider retranslating this paragraph.

After some research and discussion, the section “Does it work?” was rewritten, with particular emphasis on domain names and phishing in browsers. Some text was also added about how registries deal with phishing.

There were also various changes to the section “Further Reading”.

Comments are being sought on the revised section of this article entitled Does it work? prior to final completion. Please send any comments to www-international@w3.org (subscribe). We expect to publish a final version in one to two weeks.

Read the article

Recent developments enable you to add non-ASCII characters to Web addresses. This article provides a high level introduction to how this works. It is aimed at content authors and general users who want to understand the basics without too many gory technical details.

By Richard Ishida, W3C.