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

断行的方法 (Approaches to line breaking)

Thanks to Fuqiao Xue for providing this translation.

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.

HTML中的语言信息（教程） (Working with language in HTML)

Thanks to Fuqiao Xue for providing this translation.

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.

双向文本：Unicode控制字符还是标记语言？ (Unicode controls vs. markup for bidi support)

Thanks to Fuqiao Xue for providing this translation.

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.