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.
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.
“Ruby” are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This document proposes a set of CSS properties associated with ruby elements. They can be used in combination with the ruby elements of HTML.
The present Working Draft prepares the ground for the specification to be changed in a number of areas. Motivations for these changes include introduction of requirements arising from the Requirements for Japanese Text Layout document, updates to the handling of bopomofo ruby, and most importantly adaptations needed to support the new ruby markup model being introduced by HTML5.
Links were updated in the Accessibility and Font Selection sections, and in the Further Reading section.
The paragraph in the Page Rendering section that read “This is not implemented in the current version of Microsoft Internet Explorer, but does work in other browsers such as Mozilla” was removed, since this feature has been supported in IE since version 8 and for longer in the other major browsers.
The translations were updated with the same changes.
The whole article was largely rewritten. The list of browsers was reduced to just major browsers, but additional information on these was provided and the information was brought up to date. Further additions include a comment on IP-based negotiation, and a new section on levels of detail in language tags.
Translators should consider retranslating the whole article.
A new section “Decision 6: Extension subtags” was added to refer to the new u extension, registered by the Unicode Consortium to add information about language or locale behavior.
This change produced editorial changes to the second subsection following the new text, now title “Grandfathered tags”.
The section “Further Reading” was also overhauled.
Translators should consider retranslating the affected sections.
The section “Extension and private-use subtags” was updated to incorporate the new u extension, registered by the Unicode Consortium to add information about language or locale behavior. Editorial improvements were also added to the description of private use subtags in that section.
Translators should consider retranslating the section “Extension and private-use subtags”.