The article The byte-order mark (BOM) in HTML was updated significantly to reflect the fact that the byte-order mark in UTF-8 is less problematic now than it used to be, and that it has a higher precedence than the HTTP header for character encoding detection.
The article was largely rewritten, and now incorporates the relevant information that used to be in the article “Display problems caused by the UTF-8 BOM”. That article has now been decommissioned.
German, Spanish, Russian and Ukrainian translations need to be updated. Translators, please contact Richard Ishida (firstname.lastname@example.org) for the source text.
Minor editorial changes have been made to Unicode in XML and other Markup Languages to fix one typo (“accent” to “acute” in Table 3.1) and update references to the Unicode Standard in the Introduction and References section.
Substantive updates are currently on hold, pending final decisions relating to new developments to be introduced with HTML5.
This document is simultaneously published by the Unicode Consortium as Unicode Technical Report #20.
The article Background images that support localization was updated as follows:
- A note was added at the beginning of the background section, mentioning that CSS now enables you to create the examples in the article, where appropriate, and that the article now contains pointers to live code samples using CSS.
- The first sentence of each section describing a technique was changed to better position and introduce the section.
- A sentence was added to the end of each of the above sections, pointing to an example of how CSS could be used to reproduce that example, for browsers that support it.
- ” Internet Explorer and Opera will split the word and the hyphen will appear at the end of the line” was changed to “recent versions of major browsers will split the word and the hyphen will appear at the end of the line”
- The section “By the way” was removed.
Spanish, Russian and Ukrainian translations need to be updated. Please contact Richard Ishida (email@example.com) for the source text. In the meantime, the note and the link text have been added to those translations in English, but not the other additions.
Just Published! New Version of Working Group Note, Requirements for Japanese Text Layout (日本語組版処理の要件)
Requirements for Japanese Text Layout describes requirements for Japanese layout realized with technologies like CSS, SVG and XSL-FO. For non-Japanese speakers it provides access to a wealth of detailed and authoritative information about Japanese typesetting. The document is mainly based on a standard for Japanese layout, JIS X 4051 and its authors include key contributors to that standard. However, it also addresses areas which are not covered by JIS X 4051.
This second version of the document contains a significant amount of additional information related to hanmen design, such as handling headings, placement of illustrations and tables, handling of notes and reference marks, etc.
A Japanese version is also available.
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.