Category: New resource
The Internationalization Activity home page has recently been ported to WordPress. This means that the URIs for the various RSS feeds have changed. You can find the new links at the page W3C I18n news filters and RSS feeds.
The current URIs will continue to work for a short while, to support the transition, but you should change as soon as possible.
URIs for category filters have also changed, as have those for search key text within posts (useful for finding the history of a particular article or document). The latter have been converted to tags.
One tutorial and two articles have been updated, and a new article has been created from material that was moved out of the tutorial. The updates all involve major rewrites of the former text. These changes incorporate up-to-date information about how language declarations are handled in HTML5, and generally refresh and improve the previous material.
The new articles are:
Working with language in HTML (tutorial)
All articles use a new HTML5-based template with additional change to the boilerplate code.
How do people’s names differ around the world, and what are the implications of those differences on the design of forms, databases, ontologies, etc. for the Web?
People who create web forms, databases, or ontologies are often unaware how different people’s names can be in other countries. They build their forms or databases in a way that assumes too much on the part of foreign users. This article introduces you first to some of the different styles used for personal names, and then some of the possible implications for handling those on the Web.
By Richard Ishida, W3C.
The ‘i18n checker‘ is a free service by W3C that provides information about internationalization-related aspects of your HTML page, and advice on how to improve your use of markup, where needed, to support the multilingual Web.
This latest release uses a new user interface and redesigned source code. It also adds a number of new tests, a file upload facility, and support for HTML5.
This is still a ‘pre-final’ release and development continues. There are already plans to add further tests and features, to translate the user interface, to add support for XHTML5 and polyglot documents, to integrate with the W3C Unicorn checker, and to add various other features. At this stage we are particularly interested in receiving user feedback.
Try the checker and let us know if you find any bugs or have any suggestions.
An updated version of Working with Time Zones has just been published as a Working Group Note.
Date and time values can be complex and the relationship between computer and human timekeeping systems can lead to problems. The working group has updated this version to contain more comprehensive guidelines and best practices for working with time and time zones in applications and document formats. Use cases are provided to help choose an approach that ensures that geographically distributed applications work well. This document also aims to provide a basic understanding and vocabulary for talking about time and time handling in software.
Editor: Addison Phillips, Lab126.
Some articles are brand new and others were originally part of a tutorial, but have been updated and amplified to bring HTML5 to the fore and incorporate feedback from various readers. The articles are:
- Character encodings: Essential concepts
- Choosing & applying a character encoding
- Declaring character encodings in HTML
- The byte-order mark (BOM) in HTML
- Normalization in HTML and CSS
- Characters or markup?
Together these articles, with several other existing articles that were updated at the same time, provide practical advice to content authors on how to handle character encodings in HTML and CSS.
Answers the question: Should I use b and i elements?
The HTML5 specification redefines b and i elements to have some semantic function, rather than purely presentational. However, the simple fact that the tag names are ‘b’ for bold and ‘i’ for italic means that people are likely to continue using them as a quick presentational fix.
This article explains why that can be problematic for localization (and indeed for restyling of pages in a single language), and echoes the advice in the specification intended to address those issues.
By Richard Ishida, W3C.
This checker performs various tests on a Web Page to determine its level of internationalisation-friendliness. It also lists key internationalization settings related to character encoding, language declarations, text direction and class/id names. This information includes HTTP headers, which can be particularly useful for troubleshooting problems.
The checker is still only a prototype, so there are guaranteed to be bugs and missing features. It will slowly improve over the coming months, but it has been made available for use now since it is likely to be helpful to many people already.
FAQ-based article: Which language tag is right for me? How do I choose language and other subtags?
Following the publication of RFC 5646 earlier this year (replacing RFC 4646 as part of BCP 47), the IANA Subtag Registry now contains almost 8,000 subtags, and the list of subtag types was increased with the introduction of extended language subtags. This article tries to simplify the choice of an appropriate language tag for your needs by outlining the necessary decisions in a step-wise fashion.
By Richard Ishida, W3C.
On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note.
This document is being published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication.
The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing.
Editor: Martin Dürst.