Category: alreq

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

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.

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 W3C Internationalization Activity has updated the article How to use Unicode controls for bidi text.

This article looks at how content authors can apply direction metadata to bidirectional text when markup is not available. It was largely rewritten to incorporate more up to date information and improve the examples.

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.

The article Working with source code markup and code examples for RTL scripts is out for wide review. We are looking for comments by Wednesday 26 April.

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.

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