Category: For review
An updated version of What you need to know about the bidi algorithm and inline markup is out for wide review. We are looking for comments over the next two weeks. After the review period is over, this content will be copied to the same location as the current version of What you need to know about the bidi algorithm and inline markup and the URL of the updated version will cease to exist.
The update rewrites the article to reflect the recent changes in bidi markup in the HTML5 specification.
Technically speaking, the main change is that the
dir attribute now isolates text by default with respect to the bidi algorithm. Isolation as a default is the recommendation of the Unicode Standard as of version 6.3.
From a less technical point of view, the main advantages to the update are that the new methods introduced here reduce the need to use a new approach when the direction of content is known, and therefore makes for a much simpler transition for both content authors and browser developers to support the advances in the handling of bidirectional text content. At the same time, these approaches have good results for existing legacy content.
Please send comments to firstname.lastname@example.org.
The Internationalization Working Group has published a Last Call Working Draft of Use Cases & Exploratory Approaches for Ruby Markup.
Comments are welcome through 24 September. As this document has already been through a review cycle, we are not anticipating major changes to arise over the coming two weeks, and hope to move it to publication as a WG Note in two to three weeks time. See the status section for information about where to send feedback if you have any.
This document aims to support discussion about what is needed in the HTML5 specification, and possibly other markup vocabularies, to adequately support ruby markup. It looks at a number of use cases involving ruby, and how well the following approaches support those use cases: the HTML5 model described in the Candidate Recommendation as of 17 December 2012, the XHTML Ruby Annotation model, and the Ruby Extension Specification proposed in February 2013.
The MultilingualWeb-LT Working Group has published a Last Call Working Draft of Internationalization Tag Set (ITS) Version 2.0. ITS 2.0 makes it easier to integrate automated processing of human language into core Web technologies. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage processing based on the XML Localization Interchange File Format (XLIFF), as well as the Natural Language Processing Interchange Format (NIF). Comments are welcome through 10 September.
The draft implements all changes since the previous publication of 11 April 2013. There are no remaining open issues. The Working Group is planning to finalize ITS 2.0 now: this is your last time to provide feedback! The Last Call period ends 11 June.
ITS 2.0 provides metadata to foster the adoption of the multilingual Web.
The Internationalization Working Group has published a First Public Working Draft of Requirements for Hangul Text Layout and Typography and is looking for feedback.
This document describes requirements for general Korean language/Hangul text layout and typography realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a project to develop the international standard for Korean text layout.
A Korean version of the document is also available (한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항), but the English version is the authoritative version.
Comments are requested on the following proposed updates to material on the Internationalization site, prior to final publication. NOTE THAT the articles are in a temporary location, and will be moved to their final location after the review.
Text direction and structural markup in HTML
This article has been created from material formerly in the tutorial “Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts” and augmented with information about new HTML5 markup constructs that are beginning to see adoption. It should be regarded as a new article, focusing on applying bidi markup to document- and block-level situations and to forms.
What you need to know about the bidi algorithm and inline markup
This is an update of an existing article. It has been almost completely rewritten. The most significant changes are the new parts describing how to apply the new HTML5 constructs which are beginning to see adoption. Additional changes will be needed as HTML5 bidi markup is finalised over the coming months. The article also proposes a simpler way to approach markup of bidi text, particularly useful for those with less experience, that relies less on a deep understanding of the issues involved.
Visual vs. logical ordering of text
This is a new article created from material that has been removed from the previously mentioned material. It was removed into a separate article because visual ordering is much less important these days, and to avoid duplication. Only a few changes have been made to the content itself.
Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts
This tutorial has been modified to bring it in line with the current tutorial format. Rather than contain duplicate content, it now introduces the novice to key concepts and points off to useful further reading in an organized fashion. It has been completely rewritten.
Please send any comments over the next two weeks to email@example.com (subscribe).
We hope to publish a final version shortly after that.
Comments are requested on the following proposed update of the article The byte-order mark (BOM) in HTML prior to final publication. NOTE THAT the article is in a temporary location, and will be moved to its final location after the review.
The majority of the article has been rewritten, with the aim of reducing the previous warnings against using the BOM for UTF-8 documents. Also taken into account is the change to the HTML5 spec that raises the precedence of the BOM versus the HTTP header in terms of character encoding declaration.
We hope to publish a final version at the beginning of the New Year.
This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0.
ITS 2.0 is designed to foster the creation and localization of multilingual Web content, focusing on HTML5, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF), and language technology applications like machine translation or named entity annotation. In addition to HTML5 and XML, algorithms to convert ITS attributes to NIF is provided.
Last Call means that the MultilingualWeb-LT Working Group feels that ITS 2.0 is ready to move to recommendation. If you have comments on the document, please send them to the list mentioned in the document status before 10 January.
A new version of Internationalization Tag Set (ITS) 2.0 draft has just been published as a Working Draft.
ITS 2.0 responds to current and future needs to extend ITS 1.0, that is: provide metadata (ITS “data categories”) also for HTML5, use the data categories for RDF, and add new data categories relevant for localization and language technologies.
In addition to various clarifications and smaller changes, this second version of the document provides several new data categories discussed during the MultilingualWeb workshop in Dublin in June (e.g. Domain and Locale Filter).
Please take a look at the new version, and send any comments to firstname.lastname@example.org (subscribe at the archive main page). Use “ITS 2.0 WD Comment” at the beginning the subject line of your email, and add something descriptive after it.
Send any comments before the end of August. We are planning to publish a new working draft in late August, and a feature complete “last call” working draft in November.
Use Cases & Exploratory Approaches for Ruby Markup looks at a number of use cases involving simple and complex ruby, and considers which are supported by the current markup models in the HTML5 and XHTML Ruby Annotation specifications. Where a use case is not supported by the HTML5 model, it provides suggestions about how the markup model could be adapted to better support those use cases. In each case, pros and cons of the approach are listed, but the document does not attempt to impose a particular solution.
The hope is that implementers and standards developers will take the information and suggestions in this document as a starting point for developing a markup model for ruby in HTML5 that fully supports the use cases.
This first public working draft was published by the W3C Internationalization Core Working Group. The editor is Richard Ishida (W3C).