Monthly Archives: November 2008

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

]]

Thanks to Ana Backstone the article “Dates and Time” has now been translated into Polish (language negotiated).

Thanks to Sebastian Backstone the FAQ-based article “CSS vs. markup for bidi support” has now been translated into Polish (language negotiated).