Thanks to Samuel Chong the FAQ-based article “Using <select> to Link to Localized Content” has now been translated into Traditional Chinese.

This article was updated to add and remove browser information and correct some text. For a detailed list of changes read the full post.

Translators should consider retranslating the whole article.

In the list of command sequences, removed entries for Mozilla, Netscape Navigator, IE Mac, Galeon, and Lynx, since those are described in the location pointed to just below. Added entries for Firefox 3, Google Chrome and Konqueror.

Changed

Some of the server-side language selection mechanisms require an exact match to the Accept-Language header. If a document on the server is tagged as fr (French) then a request for a document matching fr-CH (French as spoken in Switzerland) will fail.

to

Some of the server-side language selection mechanisms will not match a long language tag in an Accept-Language header with a shorter tag associated with a document. If a document on the server is tagged as fr (French) then a request for a document matching fr-CH (French as spoken in Switzerland) will fail.

At the end of February, Felix Sasaki left the W3C to take up a post at the University of Applied Sciences at Potsdam in Germany.

We wish Felix success for the future, and thank him for his dedication and hard work in supporting the internationalization effort for the past four years.

Thanks to Gaston Diego Valente the FAQ-based article “CSS vs. markup for bidi support” has now been translated into Portuguese.

Thanks to Gaston Diego Valente the FAQ-based article “CSS vs. markup for bidi support” has now been translated into Spanish.

Thanks to Kamil Wiśniewski the article “Text size in translation” has now been translated into Polish.

See the results

These tests check whether and how a user agent displays list numbering when the value of the CSS list-style-type property is set to armenian, lower-armenian and upper-armenian.

A number of errors in the tests were corrected and the results page was rewritten to reflect the changes and results for latest versions of major browsers.

Thanks to Ana Backstone the FAQ-based article “Display problems caused by the UTF-8 BOM” has now been translated into Polish (language negotiated).

Thanks to Ana Backstone the FAQ-based article “Monolingual vs. multilingual Web sites” has now been translated into Polish (language negotiated).

Right-to-left scripts include Arabic, Hebrew, Thaana and N’ko, and are used by a large number of people around the world. If you are new to dealing with bidirectional text, getting it to display correctly can sometimes appear complex and confusing, but it need not be so. If you have struggled with this or have yet to start, this tutorial should help you adopt the best approach to marking up your content. It also explains enough of how the bidirectional algorithm works for you to understand much better the root causes of most problems, and it addresses some common misconceptions about ways to deal with markup for bidirectional content

After reading this tutorial you should:

• create effective SVG Tiny 1.2 content containing text written in the Arabic or Hebrew (or other right-to-left) scripts
• understand the basics of how the Unicode bidirectional algorithm works, so that you can understand why bidirectional text behaves the way it does, and how to work around problems
• take decisions about the appropriateness of alternatives to markup