Category: jlreq

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.)

Until now, only Gecko browsers (eg. Firefox) provided support for CSS counter styles, but an update of Blink last week brought very welcome support to a much wider range of users (via browsers such as Chrome and Edge, etc.).

To coincide with this release, the Internationalization WG updated the WG Note Ready-made Counter Styles. This contains templates for counter styles used by various cultures around the world. It can be used as a reference for those wishing to add user-defined counter styles to their CSS style sheets.

The changes include the addition of new styles for scripts including adlam, hanifi-rohingya, lepcha, meetei, santali, ethiopic and chinese. Instructions were also added for those wanting to use different suffixes or prefixes, according to the context in which the counter style is used.

An editorial update of Requirements for Japanese Text Layout has been published. The key changes include the following:

• Fixes for various errata, and improved wording in a number of locations.
• Merge of English and Japanese versions into a single document, with switches that allow readers to view the text in either language, or both. A particular language can also be requested via the URL (for example, like this: English, Japanese).
• Assignment of link targets to each list item and note, making it possible to point into the document in a more fine-grained way.

—

編集上の修正を行った日本語組版処理の要件を公開しました。主要な変更点は以下の通りです。

・いくつかの誤りを訂正し、多くの箇所の表現を改善しました。
・日本語・英語版を単一ページに統合し、読者が各言語単独または両方を含む形で表示できるようにしました。(英語もしくは日本語表示のように)各言語単独で表示するURLも利用可能です。
・文書中の各リスト項目とノートにリンクアンカーを追加し、より細かく文書の特定箇所へリンクできるようになりました。

In preparation for publication as a Working Group Note, we are seeking wide review of the document Rules for Simple Placement of Japanese Ruby. We are looking for comments by Friday 26 July.

The Japanese layout requirements document describes some complex aspects of ruby handling, and frequently offers alternative possible approaches. This document provides a single, simple set of rules for placement of Ruby text in Japanese typography which can be used as a minimal baseline by implementers and spec developers.

Please send any comments as github issues.

The W3C Internationalization Activity has just published First Public Working Drafts for 21 documents that explore gaps in language support on the Worldwide Web. Some of these documents are from individual contributors, whereas others are the result of work in a language enablement task force. The list below points to the location of the FPWD and also to the relevant group home page or to the relevant GitHub repository where the work was done.

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

Arabic & Persian Gap Analysis
https://www.w3.org/TR/alreq-gap/
https://github.com/w3c/alreq/

Chinese Layout Gap Analysis
https://www.w3.org/TR/clreq-gap/
https://github.com/w3c/clreq/

Ethiopic Layout Gap Analysis
https://www.w3.org/TR/elreq-gap/
https://github.com/w3c/elreq/

Dutch Gap Analysis
https://www.w3.org/TR/latn-nl-gap/
https://github.com/w3c/eurlreq/

Georgian Gap Analysis
https://www.w3.org/TR/geor-gap/
https://github.com/w3c/eurlreq/

Modern Greek Gap Analysis
https://www.w3.org/TR/grek-gap/
https://github.com/w3c/eurlreq/

Hungarian Gap Analysis
https://www.w3.org/TR/latn-hu-gap/
https://github.com/w3c/eurlreq/

Bengali Gap Analysis
https://www.w3.org/TR/beng-gap/
https://github.com/w3c/iip/

Devanagari Gap Analysis
https://www.w3.org/TR/deva-gap/
https://github.com/w3c/iip/

Gurmukhi Gap Analysis
https://www.w3.org/TR/guru-gap/
https://github.com/w3c/iip/

Gujarati Gap Analysis
https://www.w3.org/TR/gujr-gap/
https://github.com/w3c/iip/

Tamil Gap Analysis
https://www.w3.org/TR/taml-gap/
https://github.com/w3c/iip/

Japanese Gap Analysis
https://www.w3.org/TR/jpan-gap/
https://github.com/w3c/jlreq/

Inuktitut & Cree Gap Analysis
https://www.w3.org/TR/cans-iu-cr-gap/
https://github.com/w3c/amlreq/

Cherokee Gap Analysis
https://www.w3.org/TR/cher-gap/
https://github.com/w3c/amlreq/

Lao Gap Analysis
https://www.w3.org/TR/laoo-gap/
https://github.com/w3c/sealreq/

Khmer Gap Analysis
https://www.w3.org/TR/khmr-gap/
https://github.com/w3c/sealreq/

Javanese Script Gap Analysis
https://www.w3.org/TR/java-gap/
https://github.com/w3c/sealreq/

Thai Script Gap Analysis
https://www.w3.org/TR/thai-gap/
https://github.com/w3c/sealreq/

Mongolian Gap Analysis
https://www.w3.org/TR/mong-gap/
https://github.com/w3c/mlreq/

Tibetan Gap Analysis
https://www.w3.org/TR/tibt-gap/
https://github.com/w3c/tlreq/

The Internationalization Working Group has published a First Public Working Draft of Rules for Simple Placement of Japanese Ruby. This document provides a simple set of rules for placement of ruby text in Japanese typography that can be used as a minimum baseline for implementers and specification writers. It was developed by the JLReq (Japanese Layout) Task Force as a companion to Requirements for Japanese Text Layout 日本語組版処理の要件（日本語版）.

Ruby is the name given to the small annotations in Japanese content that are rendered alongside base text, usually to provide a pronunciation guide, but sometimes to provide other information.

This article introduces a number of basic concepts needed to understand other articles that deal with characters and character encodings.

The article has been updated with explanations of the terms ‘user-perceived character’, ‘grapheme-cluster’, ‘typographic character unit’, and ‘glyph’, and a warning about the vague use of the term ‘character’.

Read the article Character encodings: Essential concepts.

This article gives a high level summary of various typographic strategies for wrapping text at the end of a line, for a variety of scripts.

Read the article.

The article Approaches to line breaking has been significantly revised and is out for another wide review. We are looking for comments by Thursday 2 August.

This article gives a high level summary of various typographic strategies for wrapping text at the end of a line, for a variety of scripts. It complements the article Approaches to full justification.

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.)