Category: New draft
ITS 2.0 responds to needs that emerged since the creation of ITS 1.0 in 2007. First, ITS 2.0 focuses on HTML5. We can expect that huge amounts of Web content will be produced using HTML5 in the future, and ITS 2.0 will provide the means to properly internationalize and localize HTML5, using both human translation or language technologies like machine translation.
In addition, ITS 2.0 builds bridges to the Semantic Web area, by providing mechanisms to re-use ITS metadata (so-called “data categories”) with RDF.
Finally, ITS 2.0 defines new data categories that are demanded by the localization and language technology communities.
The development of this first draft of ITS 2.0 would not have been possible without the MultilingualWeb project: via MultilingualWeb, stakeholders of quite diverse communities have provided input to the initial metadata definitions. The W3C Internationalization Activity is now the place for these communities to move that metadata and its implementations forward.
We very much welcome feedback also from outside the Working Group – see issues discussed within the Working Group. Please send your comments to firstname.lastname@example.org. Use “ITS 2.0 WD Comment” at the beginning the subject line of your email, and add something descriptive after it. The archives for this list are publicly available.
Editors: Dave Lewis (TCD), Arle Lommel (DFKI), Felix Sasaki (DFKI/W3C Fellow), Jirka Kosek (UEP)
Over the past five years since its release in 2007 the Internationalization Tag Set (ITS) has shown itself to be a very powerful tool for simplifying the translation of XML content, but a lot has changed since then as improved technologies to support translation have emerged and we have seen greater levels of integration between content production and translation. As a result new needs have emerged and the W3C’s MultilingualWeb-LT Working Group was formed to develop ITS version 2.0 (ITS 2.0) to respond to these needs.
Requirements for Internationalization Tag Set (ITS) 2.0 gathers metadata categories – essentially items like ways to indicate whether or not specific text should be translated, support for machine translation, and so forth – developed within the MultilingualWeb-LT Working Group. The proposed metadata targets web content (primarily HTML5) and “deep Web” content, such as content stored in a content management system (CMS) or XML files from which HTML pages are generated, that facilitates its interaction with multilingual technologies and localization processes.
In order to ensure that the proposed metadata categories reflect the needs of the organizations that produce and translate content, interested parties should review the document and send comments to email@example.com. (You can also join the public discussion list and view its archive). We also invite you to review the issues discussed within the Working Group.
We will discuss the draft at the upcoming MultilingualWeb workshop and plan to publish a new version of the document incorporating public feedback by the end of June 2012, followed by a first draft publication of the ITS 2.0 specification.
(If you are interested in taking a more active role in working on ITS 2.0 you may also register for the Dublin workshop, at no fee, until May 30. See the call for participation for more details.)
Editors: Dave Lewis (TCD), Arle Lommel (DFKI), Felix Sasaki (DFKI/W3C Fellow)
The Internationalization Core Working Group has reached consensus to stop working on Web Services Internationalization (WS-I18N). It was published as a Working Group Note for archival reasons and is no longer being progressed along the W3C’s Recommendation Track. The only changes to this document since the last Working Draft are the addition of the note just above, and a correction to the links pointing to what was known as the Olson timezone database, which is now hosted by IANA.
A new version of the Character Model for the World Wide Web 1.0: Normalization was published. The only significant change was a note to clarify that content of the Working Draft is currently out of date, and the Internationalization Core Working Group intends to substantially alter or replace the recommendations found in this document with very different recommendations in the near future.
A new version of Requirements for Japanese Text Layout has just been published as a Working Draft.
The plan is to replace the current W3C Working Group Note with the content of this new Working Draft after a period of review.
This document describes requirements for general Japanese layout realized with technologies such as CSS, SVG and XSL-FO. It is also being used by developers of other technologies, such as ebooks. The document builds on and further develops the Japanese standard for text layout, 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.
Please take a look at the new version, which is available in English and Japanese, and send any comments to firstname.lastname@example.org (subscribe at the archive main page). Use “[JLReq]” in the subject line of your email, followed by a brief subject.
Send any comments before the end of December. We hope to publish the final version of the updated Working Group Note early in the New Year.
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.
“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.
Comments are being sought on a new draft of the W3C Note “Working with Time Zones” prior to final release. The new document provides guidelines and best practices for working with time and date values and how time zones affect applications and document formats.
Editor: Addison Phillips, Lab126.
This document arose out of the frustrations of people who have to work with bidirectional text on the Web in everyday practical situations. For example, it covers issues related to re-use of fragments of text in various new locations by web apps or scripts, or situations where users need to type in or send bidirectional form data. It proposes additions to the HTML5 specification for such situations, which are not covered by the current HTML specification. Many of the ideas in the document, however, are also relevant to markup formats in general, and there are some implications for CSS and XSL-FO (which we hope to address more directly in a subsequent document).
Please send comments on this document to email@example.com. Join the list and view the archive). We hope to publish a new version of the document, incorporating feedback, in about a month (depending on feedback received). We will then ask the HTML WG to review that version.
Editor: Aharon Lanin, Google.
The Internationalization Core Working Group has published an updated Working Draft of Best Practices for Authoring HTML: Handling Right-to-left Scripts.
This document provides advice for the use of HTML markup and CSS style sheets to create pages containing languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
The Working Group believes this document is complete and does not anticipate any substantive changes. This draft is provided as a last chance for review and feedback before publication as a Working Group Note.
Please send comments on this document to firstname.lastname@example.org (publicly archived) by 28 July 2009.
Editor: Richard Ishida.