Category: klreq

All 3 major browser engines now support the ability to create custom counter styles.

This is a significant step forward in enabling fully interoperable list numbering and other counters that reflect local approaches, especially for languages with smaller speaker populations.

See the Gap report.

See also Ready-made Counter Styles to use or adapt almost 200 suggested patterns from around the world.

By default, in runs of Latin alphanumeric text the letters are rotated 90º and run down the page. However, in some instances the alphanumerics need to stand upright. For example, this is important for acronyms.

This is now supported, using CSS, in all 3 major browser engines.

See the Gap report.

This document describes and prioritises gaps for the support of Korean language on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

The first public working draft is published to encourage users and experts to review the information it currently contains, and provide any additional information that may be relevant to supporting users of the Korean language on the Web.

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.

The Ready-made Counter Styles document provides ready-made definitions for counter styles and covers the needs of a range of cultures around the world. The code snippets provided in the document can be included in style declarations by simply copying and pasting, or they can be use as a starting point and modified as desired.

This update brings the total number of style templates to 177, covering 44 writing systems.

Substantial changes were also made to the styling and presentation. Each template is now accompanied by a set of examples, as well as an icon that copies the template to your clipboard in a single click. Another icon points to MDN’s roundup of browser support for named styles. Extensions to cover affix variants are now expressed in terms of the extends syntax.

Fixes were applied for tai-lue and warang-citi styles.

Finally, a button is provided to allow you to turn off all counter styling for the examples. That then allows you to see which styles have built-in support in the browser you are using.

The article Font styles & font fallback has now been published.

This article provides a non-exhaustive set of examples where choice of a font style may have a practical application. The existence of these distinct styles, with their practical influence on the reading of the text, has implications for fonts on the Web – you would typically want to choose a fallback font that has the same style, if one is available. We look at some implications for generic fonts and fallback mechanisms near the end.

The article Font styles & font fallback is out for wide review. We are looking for comments by Thursday 3 November.

This article provides a non-exhaustive set of examples where choice of a font style may have a practical application. The existence of these distinct styles, with their practical influence on the reading of the text, has implications for fonts on the Web – you would typically want to choose a fallback font that has the same style, if one is available. We look at some implications for generic fonts and fallback mechanisms near the end.

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

The article Styling vertical Chinese, Japanese, Korean and Mongolian text has been updated in the following ways:

1. The sections Sideways values of writing-mode and The sideways value of text-orientation have been rewritten to replace content with more up-to-date and accurate information.
2. Browser support information has been overhauled and brought up to date.
3. In-page live code has been added to show how each feature behaves in your browser.

The article Ruby Styling provides guidance for content authors on CSS features available for styling ruby text in Japanese, Chinese, Korean, and Mongolian. It is a companion article to Ruby Markup. It includes information about what is and isn’t currently supported in major browsers.

Translators are invited to provide translations.

Please raise any comments as github issues by clicking on the “Leave a comment” link at the bottom of the article.

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.

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/