Category: For review

The article Ruby Styling is out for wide review. We are looking for comments by Thursday 14 July.

The article reviews the typical usage patterns of inline annotations for Japanese and Simplified/Traditional Chinese, and provides guidance for content authors about how to use features of the CSS Ruby spec to achieve the rendering they want. It also reports on current support for those features in the 3 major browser engines. This information should also be useful for authors writing in the Traditional Mongolian orthography.

This is a companion article to Ruby Markup, which focuses on how to mark up inline annotations.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The article RTL rendering of LTR scripts is out for wide review. We are looking for comments by Thursday 7 July.

The article suggests ways to produce runs of right-to-left text using HTML & CSS for languages that are nowadays normally written left-to-right. The use cases for this are rare, and mostly relate to academic descriptions of text in orthographies such as Chinese, Japanese, Egyptian hieroglyphs, Tifinagh, Old Norse runes, and a good number of other now-archaic scripts.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The W3C Internationalization Activity has just published First Public Working Drafts for 2 more documents that explore gaps in language support on the World Wide Web.

• Perso-arabic Kashmiri Gap Analysis
• Uighur Gap Analysis

We are looking for expert contributors who can help us move this work forward by answering questions, documenting other gaps in support, and creating tests. For more information about the program, see this 15 minute overview (slides), and see the Language Enablement overview page.

A First Public Working Draft of Developing Localizable Manifests has been published.

This document provides definitions and best practices related to the specification of manifest files and similar document formats on the Web.

Some specifications on the Web deal with defining sets of files or resources to be consumed together. A common design pattern is to provide a manifest or configuration file that defines which resources are available and how various resources should be used or to provide various kinds of metadata about a collection of resources.

The document is still at a very early stage, and shows the intent, rather than reliable detail. Public comments are welcome, please raise them as github issues.

The W3C Internationalization Activity has published a first public working draft of an Internationalization Glossary. This document provides or points to definitions for various terms related to W3C internationalization.

As well as adding new terms, we plan to point to related definitions in other locations as the document evolves.

Please send any comments to the GitHub issues list.

The article Structural markup and right-to-left text in HTML is out for wide review. We are looking for comments by Thursday 13 May.

This article looks at ways of handling text direction for structural markup in HTML, ie. at the document level and for elements like paragraphs, tables and forms. The article has been largely rewritten to take into account recent developments in HTML and CSS. A section was added to describe the use of logical properties. The text was make more concise.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The article Can we derive base direction from language? is out for wide review. We are looking for comments by Thursday 1 April.

Sometimes people wonder whether it’s possible to obtain a definitive list of language tags which indicate a RTL base direction, so that there would be no need for separate direction metadata. This article looks into whether that is really feasible. (Spoiler: The W3C Internationalization Working Group believes it is not a feasible approach.)

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The article Use cases for bidi and language metadata on the Web is out for wide review. We are looking for comments by Thursday 11 March.

The W3C Internationalisation Working Group recommends that data formats and string data are always associated with information about text direction and language. This is to ensure that the data can be correctly managed when displayed to a user. This article explores use cases that substantiate the need for this type of information.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The article Typographic character units in complex scripts is out for wide review. We are looking for comments by Thurday 25 February.

CSS defines the typographic character unit as a basic unit of text for use with editing operations, however the meaning of a that term can vary according to the operation, and there are issues in working with such units in complex scripts. In this article we look at examples of some of those differences and issues.

Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)

The Editor’s Draft of the Working Group Note “Character Model: String Matching” is out for wide review. We are looking for comments by Wednesday, 21 October.

The Character Model series of documents contains background material, best practices, and recommendations for specification authors, implementers, and content authors related to the use of character encodings and Unicode on the Web. The “String Matching” document deals with specifying content restrictions and the matching of identifiers in protocols and document formats for W3C specifications.

The new revision adds two new terminology definitions (“application internal identifiers”, “user-facing identifiers”) and a new section targeted to specification authors on “Specifying Content Restrictions” (Section 3.1). The Working Group would like comments about these specific changes; comments about other aspects of the document are also welcome.

Please send any comments as github issues.