Category: New resource

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.

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

• Cyrillic Gap Analysis

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.

The Internationalization Activity has just published the following FPWD documents.

• Latin Script Resources
• Latin Gap Analysis
• Arabic Script Resources
• Hebrew Script Resources
• Chinese Script Resources

The documents related to language enablement at the W3C are being refactored to represent scripts, rather than individual languages. These 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.

The article How can I use direction metadata in native APIs? has now been published.

This article provides links to documentation in many different operating systems, programming environments, and user experience frameworks. These APIs can then be used to consume language and string direction metadata received on the Web or in other APIs or formats.

The Internationalization Activity has just published the following FPWD documents.

• Perso-Arabic Kashmiri Layout Requirements
• Urdu Layout Requirements
• Uighur Layout Requirements

These languages are all written right-to-left (based on the Arabic script) and are used in India, Pakistan, and Western China. Urdu & Kashmiri are normally written in the nastaliq writing style.

Currently, these documents mostly point to external descriptions of how the script works. They also point to relevant GitHub discussions, tests, and gap reports. This provides a convenient way to access information about a particular script/language when doing gap analysis as part of our language enablement program.

Comments welcome, via the GH links indicated at the top of each page.

The Internationalization Activity has just published the following FPWD document.

• Adlam Layout Requirements

This document was also updated.

• N’Ko Layout Requirements

Currently, these documents mostly point to external descriptions of how the script works. They also point to relevant GitHub discussions, tests, and gap reports. This provides a convenient way to access information about a particular script/language when doing gap analysis as part of our language enablement program.

Comments welcome, via the GH links indicated at the top of each page.

The Internationalization Activity has recently published the following FPWD documents.

• Khmer Layout Requirements
• Thai Layout Requirements
• Lao Layout Requirements

Thus far, these documents mostly point to external descriptions of how the script works. They also point to relevant GitHub discussions, tests, and gap reports. This provides a convenient way to access information about a particular script/language when doing gap analysis as part of our language enablement program.

Similar structural changes have been applied to the following documents, although these documents contain much more in-page content.

• Requirements for Tibetan Text Layout and Typography
• Arabic & Persian Layout Requirements

Comments welcome, via the GH links indicated at the top of each page.

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.

This document describes requirements for the layout and presentation of text in the N’Ko script when used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode. It is developed in conjunction with a document which summarizes gaps in Gurmukhi support on the Web and eBook technologies.

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 N’Ko script on the Web.

Please send comments by raising a GitHub issue for each point.

The W3C Internationalization Activity has published the article Working with source code markup and code examples for RTL scripts.

Editing markup for pages in Arabic, Hebrew, and many other languages poses challenges unless a specialized editor is available. For similar reasons, it is also difficult to include examples of bidirectional code in explainers. This page looks at some of the problems content developers and implementers of editors are likely to be faced with, and offers some advice, where possible.