Category: klreq
Posts
Requirements for Hangul Text Layout and Typography 한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항
A NEW VERSION of Requirements for Hangul Text Layout and Typography
한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항 has been published.
The content was rearranged to match the standard headings used for the W3C Language Enablement Framework. The document is still in English and Korean, with buttons to switch between.
FOR REVIEW: Styling underlines
The article Styling underlines is out for wide review. We are looking for comments by Thursday 19 March, 2026.
This article explores various ways in which CSS can be used to manage underlines for non-Latin scripts.
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.)
New article: How to make list markers stand upright in vertical text
The article How to make list markers stand upright in vertical text has been published.
In Chinese, Japanese, Korean, and Mongolian vertically-set text it is normal for list counters to sit upright above the start of the list. Until recently this was problematic, because browsers would only show the numbers lying on their side. This article describes how to make them stand upright, and the currently remaining issues to make this look perfect.
FOR REVIEW: How to make list markers stand upright in vertical text
The article How to make list markers stand upright in vertical text is out for wide review. We are looking for comments by Friday 29 April.
In Chinese, Japanese, Korean, and Mongolian vertically-set text it is normal for list counters to sit upright above the start of the list. Until recently this was problematic, because browsers would only show the numbers lying on their side. This article describes how to make them stand upright, and the currently remaining issues to make this look perfect.
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.)
New First Public Working Drafts: Bengali, Canadian Syllabics, Cherokee, Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Japanese, Javanese, Korean, Mongolian, Osage, Tamil, Tibetan
The Internationalization Activity published the following FPWD documents.
- Bengali Script Resources
- Canadian Syllabics Script Resources
- Cherokee Script Resources
- Cyrillic Script Resources
- Devanagari Script Resources
- Ethiopic Script Resources
- Georgian Script Resources
- Greek Script Resources
- Gujarati Script Resources
- Japanese Script Resources
- Javanese Script Resources
- Korean Script Resources
- Mongolian Script Resources
- Osage Script Resources
- Tamil Script Resources
- Tibetan Script Resources
The documents related to language enablement at the W3C continue and expand the work to reorganise information to represent scripts, rather than individual languages. The newly published -lreq documents should be a first port of call for information related to a given script. They point to descriptions about how the scripts work, to tests, to discussions, to type samples, and more, all organised by topic.
Comments welcome, via the GH links indicated at the top of each page.
WEB I18N GAP FIXED: Interoperable custom counter styles
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.
WEB I18N GAP FIXED: Upright alphanumerics in vertically-set text
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.
First Public Working Draft: Korean Layout Gap Analysis
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.
Updated: Ready-made Counter Styles
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.
New article: Font styles & font fallback
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.
W3C® liability, trademark and permissive license rules apply.
Questions or comments? xfq@w3.org




