Category: Update

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.

An update for the article Inline markup and bidirectional text in HTML has just been published.

This article tells you how to write HTML where text with different writing directions is mixed within a paragraph or other HTML block (ie. inline or phrasal content).

The worked examples and the descriptions of markup have been moved to a new page: Inline bidi markup examples. This and various small edits, including a new set of examples with links to live versions, are intended to make it easier to read the main article and make its advice clearer.

Send any comments via GitHub.

An editorial update of Requirements for Japanese Text Layout has been published. The key changes include the following:

• Fixes for various errata, and improved wording in a number of locations.
• Merge of English and Japanese versions into a single document, with switches that allow readers to view the text in either language, or both. A particular language can also be requested via the URL (for example, like this: English, Japanese).
• Assignment of link targets to each list item and note, making it possible to point into the document in a more fine-grained way.

—

編集上の修正を行った日本語組版処理の要件を公開しました。主要な変更点は以下の通りです。

・いくつかの誤りを訂正し、多くの箇所の表現を改善しました。
・日本語・英語版を単一ページに統合し、読者が各言語単独または両方を含む形で表示できるようにしました。(英語もしくは日本語表示のように)各言語単独で表示するURLも利用可能です。
・文書中の各リスト項目とノートにリンクアンカーを追加し、より細かく文書の特定箇所へリンクできるようになりました。

Types of language declaration describes how ‘metadata’ and ‘text-processing’ language declarations differ.

HTTP headers, meta elements and language information has been updated to read better, and the information that was to become the previously mentioned article was removed.

This article introduces a number of basic concepts needed to understand other articles that deal with characters and character encodings.

The article has been updated with explanations of the terms ‘user-perceived character’, ‘grapheme-cluster’, ‘typographic character unit’, and ‘glyph’, and a warning about the vague use of the term ‘character’.

Read the article Character encodings: Essential concepts.

An update for the article Inline markup and bidirectional text in HTML has just been published.

This article tells you how to write HTML where text with different writing directions is mixed within a paragraph or other HTML block (ie. inline or phrasal content). The article has been updated to bring it in line with recent browser developments and to simplify the guidelines. Examples are linked to live versions, and indications are given for which features are supported by which browsers.

A draft update for the article Inline markup and bidirectional text in HTML is out for wide review. We are looking for comments by Tuesday 12 December.

This article tells you how to write HTML where text with different writing directions is mixed within a paragraph or other HTML block (ie. inline or phrasal content). The article has been updated to bring it in line with recent browser developments and to simplify the guidelines. Examples are linked to live versions, and indications are given for which features are supported by which browsers.

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

In addition to various editorial improvements, the following significant changes were made to the article:

1. A “Quick answer” section was added
2. Two new subsections were added to the section about CSS escapes: “Using escapes with CSS identifiers” and “Sequences and backslashes”

For a detailed list of changes, see the GitHub commit log.

See the updated article.

The Encoding Candidate Recommendation has been updated to take into account changes made to the editor’s draft since its previous publication as a Candidate Recommendation. These changes are largely due to issues discovered during implementation.

This is a snapshot of the WHATWG document, as of 10 November 2016, and if you wish to make comments regarding this document, please raise them as github issues against the WhatWG version of the spec. Only send comments by email to www-international@w3.org if you are unable to raise issues on github. All comments are welcome.

The utf-8 encoding is the most appropriate encoding for interchange of Unicode, the universal coded character set. Therefore for new protocols and formats, as well as existing formats deployed in new contexts, this specification requires (and defines) the utf-8 encoding.

The other (legacy) encodings have been defined to some extent in the past. However, user agents have not always implemented them in the same way, have not always used the same labels, and often differ in dealing with undefined and former proprietary areas of encodings. This specification addresses those gaps so that new user agents do not have to reverse engineer encoding implementations and existing user agents can converge.

The article was edited to make it easier for non-experts to follow. An example of an encoding declaration was added, and a form to check for HTTP headers, but most of the text was also reworked.

See the updated article.