Japanese Gap Analysis

Abstract

This document describes and prioritises gaps for the support of Japanese 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.

See also General page layout & progression for features such as column layout, page turning direction, etc. that are affected by text direction.

Are the script requirements for vertically oriented text met? What about if you mix vertical text with scripts that are normally only horizontal? Do you need a switch to use different characters in vertical vs. horizontal text? Does the browser support short runs of horizontal text in vertical lines (tate-chu-yoko in Japanese) as expected? Is the orientation of characters and the directional ordering of characters supported as needed? See available information or check for currently needed data.

GitHub issue #180

It should be possible to decrease the size around the ideographic comma (1/2em) and katakana middle dot (1/4em) in numerical values in vertical text. See Exceptional Positioning of Ideographic Comma and Katakana Middle Dot.

img2_11

There is a related discussion about how to achieve this.

Tests & results: interactive test

GitHub issue #171

This issue is applicable to Japanese, Chinese & Korean.

If you place the writing-mode property with a value of vertical-rl/lr on an individual table cell in a table that overall has a horizontal direction, you would expect the text in that cell to be displayed vertically, but in some browsers it isn't, unless the height of the td element is specified.

This appears to be because the text is wrapped character-by-character (cf. Mongolian, where words are wrapped rather than characters).

Tests & results: Interactive test, Adding writing-mode:vertical-rl to a td element produces vertical text, with lines stacking RTL.
This works as expected in Gecko and Blink browsers, as well as in legacy Edge and Internet Explorer. However, Webkit browsers, leave the text horizontal but rotate the Japanese characters to the left.

Interactive test, Adding writing-mode to a span inside a td produces the expected directionality
Wrapping the text to be made vertical in a span inside the cell, and applying writing-mode:vertical-rl to that gives the expected result in Blink, but in Safari it's necessary to also apply a height setting for the text to display properly.

Browser bug reports: Blink • Webkit

Priority: Correct behaviour here is a pretty basic expectation for handling directionality in tables, but since it only occurs when the direction of the td element is different from that of the overall table, this can probably be marked as advanced.

Updates: June 2021: This gap was fixed for Blink.

GitHub issue #170

This issue is applicable to Chinese, Japanese, Korean, and Mongolian.

A common way to orient counters for lists in vertical text is to have an upright number with a dot alongside it. Alternatively, upright circled digits may be used.

vertical-lists

This is very common in printed material, but is not well supported in web pages.

Specs: css-pseudo The ::marker pseudo-element represents the automatically generated marker box of a list item, and can be styled.

The expected way to achieve this in HTML would be to use the following CSS: li::marker { text-combine-upright: all; }, however not all browsers support text-combine-upright.

A workaround might be to use fullwidth characters for counters, such as ①, ②, ③ or ⒈, ⒉, ⒊ etc., but use of such a workaround requires the availability of custom built counter styles, and not all browsers support the CSS Counter Styles specification. So that doesn't work either.

Tests & results: Interactive test, It is possible to make list counters upright in vertical text using li::marker { text-combine-upright: all; }.
Gecko and Blink based browsers now both support this behaviour. Webkit browsers do not.

Interactive test, It is possible to set list markers as upright circled numbers in vertical text using an @counter-style definition Interactive test, It is possible to set list markers as upright dotted numbers in vertical text using an @counter-style definition

Gecko and Blink based browsers now both support custom-defined counter styles. Webkit browsers do not.

Priority: It is a significant nuisance for content authoring to not be able to produce upright counters for lists. This is a very common approach to numbering lists in vertical text, and should be possible on the Web.

Browser bug reports: Chromium Webkit Webkit Mozilla

GitHub issue #169

This issue is applicable to Chinese, Japanese, Korean, and Mongolian.

The CSS text-combine-upright property works with the all value in all major browsers. However, the CSS digits value is not supported by recent version of major browser engines.

For more details, see this GitHub issue, which is being used to track this gap.

GitHub issue #168

This issue is applicable to Chinese, Japanese, Korean, and Mongolian.

The CSS text-orientation property is only supported as standard by Gecko and Blink browsers.

For more details, see this GitHub issue, which is being used to track this gap.

GitHub issue #167

This issue is applicable to Chinese, Japanese, Korean, and Mongolian.

Handling of vertical text in forms is a major gap. Only the Firefox desktop browser does a good job of this. Other browsers fail resoundingly in terms of orienting form controls vertically and displaying text vertically inside them.

For more details, see this GitHub issue, which is being used to track this gap.

If this script runs right-to-left, are there any issues when handling that? Is bidirectional text adequately supported? What about numbers and expressions? Do the Unicode bidi controls and HTML markup provide the support needed? Is isolation of directional runs problematic? See available information or check for currently needed data.

Are there any character repertoire issues preventing use of this script on the Web? Do variation selectors need attention? Are there any other encoding-related issues? See available information or check for currently needed data.

Do the standard fallback fonts used in browsers (eg. serif, sans-serif, cursive, etc.) match expectations? Are special font or OpenType features needed for this script that are not available? See available information or check for currently needed data.

This covers ways of modifying the glyphs, such as for italicisation, bolding, oblique, etc. Do italic fonts lean in the right direction? Is synthesised italicisation problematic? Are there other problems relating to bolding or italicisation - perhaps relating to generalised assumptions of applicability? See available information or check for currently needed data.

Does the script in question require additional user control features to support alterations to the position or shape of glyphs, for example adjusting the distance between the base text and diacritics, or changing the glyphs used in a systematic way? Do you need to be able to compose/decompose conjuncts, or show characters that are otherwise hidden, etc? See available information or check for currently needed data.

GitHub issue #182

When starting a new line with opening brackets after forced line break, several options exist for amount of spacing before the opening brackets, as in JLReq section 3.1.5:

This is proposed in css-text-4 as text-spacing, not implemented yet in browsers.

(tests are proposed in i18n-tests as PR).

GitHub issue #181

In Japanese text, spacing between consecutive punctuation are partly omitted as described in JLReq section 3.1.4, as follows:

This is implemented in css-text Level 4 text-spacing, not yet implemented in browsers.

(tests are proposed to i18n-tests, not yet reviewed by i18n WG nor merged)

If this script is cursive (eg. Arabic, N’Ko, Syriac, etc), are there problems or needed features related to the handling of cursive text? Do cursive links break if parts of a word are marked up or styled? Do Unicode joiner and non-joiner characters behave as expected? See available information or check for currently needed data.

Does the browser support requirements for baseline alignment between mixed scripts and in general? See available information or check for currently needed data.

Does your script need special text transforms that are not supported? Does your script convert letters to uppercase, capitalised and lowercase alternatives according to your typographic needs? Do you need to to convert between half-width and full-width presentation forms? See available information or check for currently needed data.

GitHub issue #172

Latin text and numbers embedded in Japanese text are typically proportionally-spaced, but in some cases it is best to display them as full-width characters, especially for acronyms in vertically set text. For example, if the text "国际化活动W3C万维网联盟" is displayed vertically, the 'W3C' should be full-width, upright characters rather than proportionally-spaced text running down the line.

Screenshot 2021-08-11 at 15 40 39

It's useful to be able to achieve this via styling, similar to the case conversion transforms used for Latin text.

Specs: CSS Text provides text-transform: full-width to transform text in this way.

Tests & results: Simple test, standard syntax • proprietary syntax

More tests: a-z, A-Z, punctuation, katakana, punctuation, symbols

Gecko supports this. Blink and Webkit do not.

Browser bug reports: Chromium • Webkit

Priority: The priority was set to basic by the initial reporter. This is certainly a very useful thing to have to hand when working with vertical text, in particular.

This is about how text is divided into graphemes, words, sentences, etc., and behaviour associated with that. Do Unicode grapheme clusters appropriately segment character units for your script? When you double- or triple-click on the text, is the expected range of characters highlighted? When you move through the text with the cursor, or backspace, etc. do you see the expected behaviour? (Some of the answers to these questions may be picker up in other sections, such as line-breaking, or initial-letter styling.) See available information or check for currently needed data.

Are there specific problems related to punctuation or the interaction of the text with punctuation (for example separation of punctuation from previous text, but allowing no line break between)? Are there issues related to handling of abbreviation, ellipsis, or iteration? Are there problems related to bracketing information or demarcating things such as proper nouns, etc? See available information or check for currently needed data.

This is about ways of marking text (see also specific sections dedicated to quotations and inline notes/annotations). Is it possible to express emphasis or highlight content as expected? Bold, italic and under-/over-lines are not always appropriate, and some scripts have their own unique ways of doing things, that are not in the Western tradition at all. Text delimiters mark certain items or sections off from the main text, such as book names in Chinese, quotations, head markers in Tibetan, etc, and often involve the use of punctuation. Is there any behaviour that isn't well supported, such as overlines for numeric digits in Syriac? Are there issues about the positioning or use of underlines? Some aspects related to the drawing of lines alongside or through text involve local typographic considerations. Do underlines need to be broken in special ways for this script? Do you need support for additional line shapes or widths? Does the distance or position of the lines relative to the text need to vary in ways that are not achievable? Are lines correctly drawn relative to vertical text? See available information or check for currently needed data.

GitHub issue #368

This issue is applicable to Chinese and Japanese.

Emphasis dots should be centre-aligned with the text after the letter spacing is increased.

For more details, see this GitHub issue, which is being used to track this gap. Please discuss this issue there.

GitHub issue #338

This issue is applicable to Japanese & Chinese in particular.

Issue jlreq/173 looks at basic support for boten (emphasis) marks and their positioning. This gap report describes some additional aspects of boten handling that need further investigation.

Additional requirements arose while the text was being written for CSS. They relate to text that is annotated with ruby at the same time as annotation marks. The conclusions were:

Emphasis marks go outside ruby, as shown by the emphasis dot above the ruby annotations in this example:
If ruby only spans part of the emphasised word, emphasis marks stay as close as possible to the base, as shown in the emphasis dots on either side of the ruby text.
Where a ruby annotation is hidden or empty, the emphasis marks should continue at the same height, as in the following example where the ruby element spans the whole word but no annotation is provided for the second character.

There are currently no requirements in jlreq for positioning boten marks with ruby.

[For further research] JLReq also requires that emphasis marks not appear over commas, full stops and brackets.

JLReq calls out the usual practise of using sesame shaped boten for vertical text, and bullets for horizontal. Controls for this exist in CSS, and tests show that it is supported by the browsers that support boten.

The default side for boten is to the right of vertical lines and above horizontal lines, according to JLReq. CSS controls allow this positioning to be set by the author, and in fact it is the default in both browsers that support boten for text where a lang tag identifies it as Japanese.

Gecko moves the boten marks alongside the ruby annotation, keeping the latter closest to the base. In Blink, and Webkit, the boten marks disappear when they occur over the same base as ruby annotations.

All browser engines keep the boten marks close to the base text where ruby annotations don't appear.

Interactive test, Emphasis marks go outside ruby

3.4. Emphasis Mark Position: the [text-emphasis-position property](https://drafts.csswg.org/css-text-decor-3/#text-emphasis-position-property) Indicates that the default expectation is for boten marks to appear outside the ruby, but also mentions how to hide the marks if that is your preference, or hide the ruby.

TBD: Gecko • Blink • Webkit

TBC

If the emphasis marks don't spill over to the text alongside the ruby annotations there is no indication that the text is emphasized, which is clearly a problem.

GitHub issue #173

This issue is applicable to Japanese & Chinese, in particular.

Chinese and Japanese have a native way of indicating emphasis for short ranges of inline text which involves placing a small mark above or below the characters being emphasised in horizontal text, and to the right/left in vertical text.

The actual marks used vary, depending on author preference, although some marks are more common in vertical text and others in horizontal. Typically, dots, circles, or 'sesame seed' shapes are used.

The following illustrates this: Slide0210-3107917968

For more details see notes on Japanese and Chinese.

Specs: css-text-decor CSS has several properties for displaying emphasis marks, and colouring them, positioning them, etc.

Tests & results: i18n test suite, CSS3 Text decoration, emphasis marks
The tests check for support of the most common shapes, and that the positioning can be managed.
When this gap was initially raised, Chrome (and legacy Edge) did not support display of emphasis marks. Now, however, they are supported in all 3 major engines: Gecko, Blink, and Webkit.

Are there any issues when dealing with quotations marks, especially when nested? Should block quotes be indented or handled specially? See available information or check for currently needed data.

GitHub issue #174

This issue is common across all languages that use the q element.

When a Japanese page contains a quotation in another language, the quotation marks used around that quotation (and inside it for embedded quotes) should be the Japanese ones – not those of the language of the quotation.

Currently, if the language of the quotation is declared on the q tag in HTML using the lang attribute, browsers instead set the quotation marks based on the language of the quote.

For example, if English text is quoted in a Japanese sentence surrounded by just <q>, the quotation marks will be correct:

いち「two 『three』」

However, if lang="en" is added to the q tag, the result becomes:

いち “two ‘three’”

Here is a test. There are also tests and results in the i18n test suite.

For more details, see this GitHub issue, which is being used to track this gap.

The ruby spec currently specifies an initial subset of requirements for fine-tuning the typography of phonetic and semantic annotations of East Asian text, including furigana, pinyin and zhuyin fuhao systems. Is is adequate for what it sets out to do? What other controls will be needed in the future? What about other types of inline annotation, such as warichu? (For referent-type notes such as footnotes, see below.) See available information or check for currently needed data.

GitHub issue #318

This issue is applicable to Japanese and Chinese.

Warichu (inline cutting note) is a type of inline notation, where two lines of small characters are inserted into the text. Warichu divides a line into two sub lines. Inline cutting note is usually used in vertical writing mode. It is very infrequently used in horizontal writing mode. (see Inline Cutting Note (Warichu))

img2_4_1

Specs: CSS doesn't yet propose a way of achieving warichu.

Tests & results: tbd

Browser bug reports: tbd

Priority: The frequency of use of the inline cutting note is not so high. However, the inline cutting note is very important for study guides, travel guides, reference books, encyclopedias and manuals, because it is very effective for inserting notes at the point in the text where they are needed. For these reasons, the priority assigned here is advanced.

GitHub issue #255

This issue is applicable to all languages that use ruby markup.

If text is marked up for ruby, using the interleaved markup approach currently required by the HTML spec, a browser's in-page search no longer recognises the text. For example, if you search for 東京 on a page that has this markup:

<ruby><rb>東<rt>とう<rb>京<rt>きょう</ruby>

the search will fail to locate the word.

Note that a tabular arrangement of markup, such as

<ruby><rb>東<rb>京<rt>とう<rt>きょう</ruby>

would work fine but, although it is parsed correctly, this tabular markup is not displayed correctly by Blink or Webkit currently, and therefore the HTML specification has obsoleted the rb and rtc elements.

Specs: The HTML specification currently blocks the workaround (which is to use tabular markup), but a solution needs to also be found for the interleaved markup. That work is in preparation in the W3C HTML Working Group, which will spec out the full ruby model in a way that can be incorporated into the WhatWG spec in future.

Tests & results: Interactive test, In page search will find text that has ruby annotations in interleaved markup
Blink and Webkit browsers all fail to recognise strings when they have ruby text. Gecko appears to recognise the search string in the ruby element, but doesn't display the highlight correctly (see https://github.com/w3c/jlreq/issues/255#issuecomment-1278066359). (If you copy the text, you also get the ruby text, but not the one at the end of the ruby element.)

Interactive test, In page search will find text that has ruby annotations in tabular markup
Gecko, Blink, and Webkit browsers all recognise strings when they have ruby text arranged in tabular format, however support for that arrangement was removed from the HTML spec because currently only Gecko and Amazon have browsers that display the results correctly.

Browser bug reports: Gecko • Blink • Webkit

Priority: This is an obstacle to basic interaction with web pages, especially while the HTML spec blocks the use of tabular markup.

GitHub issue #177

For background information read Aligning annotations and bases.

Fine control in HTML over the placement of ruby annotations relative to the base require the availability of the CSS property ruby-align. This only works in Firefox, and sometimes in Edge with proprietary syntax. It doesn't work for Chrome or Safari. See results for major browsers.

The impact of this is probably more important for advanced typographic layout.

GitHub issue #176

In order to get double-sided ruby to appear on either side of the base text in HTML, you need the CSS ruby-position property to work with the value under. It currently works per the standard with Gecko and Blink, but doesn't work with Webkit (or EdgeHTML). It does work in Webkit with the proprietary -webkit prefix and value after in Webkit (but doesn't work with EdgeHTML).

See test results for standard syntax and proprietary syntax.

Try interactive tests.

Double-sided ruby doesn't appear often in Japanese text, but it is used, and should be available to content authors.

Related browser bugs: Chromium Webkit Webkit

GitHub issue #175

This issue is applicable to all languages using ruby annotations. (See: jlreq)

The basic pattern of 'tabular' markup is ruby-base ruby-base ... ruby-text ruby-text .... An advantage to this approach is that it enables you to style the ruby text to appear inline in such a way that all the ruby text for a word follows that word together. Inline styling can be useful in space-constrained situations, where it would be too difficult to read small ruby characters. Read more.

This also makes certain applications of double-sided ruby impossible when the ruby on each side of the base spans a different set of base characters.

When text is marked up in mono-ruby way, searching will not work well. If you have the following markup

<p><ruby>漢<rt>かん</rt>字<rt>じ</rt></ruby></p>

and search for the base text "漢字" in a browser, you will not get a result. Tabular markup could solve this problem. (See https://github.com/w3c/i18n-issues/issues/2 for a similar report raised by Japanese & Chinese users.)

Specs: issue 1771 rb and rtc element should be removed from the list of obsolete features Open.
html has actually removed markup for rb and rtc elements, which would be needed to make this work. The parser, however, supports the use of the markup still.
css-ruby-1 Describes how the tabular approach will work for CSS.

Tests & results: i18n test suite, HTML5, the ruby element and its children
Gecko supports display of ruby using the tabular model. Blink, and Webkit do not correctly support display. However, all browsers recognise the rb and rtc elements, and allow them to be styled or manipulated using scripting.

Kindle's ePub implementation also implements the tabular model, although not rtc.

Browser bug reports: Gecko • Blink • Webkit

Priority: The limitations created by the lack of the tabular model are all basic in nature. None more so that the impairment for searching, since browsers have not been incentivised to fix that in any other way. The obsoletion of the rb and rtc elements by the HTML spec runs the risk that browser engines are not implementing the tabular model.

If the script has its own set of number digits, are there any issues in how they are used? Does the script or language use special format patterns that are problematic (eg. 12,34,000 in India)? What about date/time formats and selection - and are non-Gregorian calendars needed? Do percent signs and other symbols associated with number work correctly, and do numbers need special decorations, (like in Ethiopic or Syriac)? How about the management of personal names, addresses, etc. in web pages: are there issues? See available information or check for currently needed data.

Does the browser capture the rules about the way text in your script wraps when it hits the end of a line? Does line-breaking wrap whole 'words' at a time, or characters, or something else (such as syllables in Tibetan and Javanese)? What characters should not appear at the end or start of a line, and what should be done to prevent that? See available information or check for currently needed data.

Is hyphenation used for your script, or something else? If hyphenation is used, does it work as expected? (Note, this is about line-end hyphenation when text is wrapped, rather than use of the hyphen and related characters as punctuation marks.) See available information or check for currently needed data.

When text in a paragraph needs to have flush lines down both sides, does it follow the rules for your script? Does the script need assistance to conform to a grid pattern? Does your script allow punctuation to hang outside the text box at the start or end of a line? Where adjustments are need to make a line flush, how is that done? Do you shrink/stretch space between words and/or letters? Are word baselines stretched, as in Arabic? What about paragraph indents, or the need for logical alignment keywords, such as start/end, rather than left/right? See available information or check for currently needed data.

Some scripts create emphasis or other effects by spacing out the words, letters or syllables in a word. Are there requirements for this script/language that are unsupported? (For justification related spacing, see below.) See available information or check for currently needed data.

GitHub issue #312

This issue is applicable to Chinese and Japanese.

In Japanese composition, it is usually recommended to apply extra spacing between Japanese and Western text to increase the recognition of Western text.

Currently, browsers do not support this feature, so content authors have to work around the problem by adding spaces manually.

For more details, see this GitHub issue, which is being used to track this gap. Please discuss this issue there.

GitHub issue #265

This issue applies to all languages that use letter-spacing.

Currently browsers that apply letter-spacing do so by adding a space after every letter in the text that is tracked. This results in a superfluous space at the end of the range, which creates an inappropriate gap before the following text. Letter spacing at the end of a line makes the line look misaligned in justified or right-justified text. It also has implications for text that has other styling, such as an outline or a coloured background, at the same time as being stretched.

For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.

The CSS Counter Styles specification describes a limited set of simple and complex styles for counters to be used in list numbering, chapter heading numbering, etc.The rules plus more counter styles (totalling around 120 for over 30 scripts) are listed in the document Ready-made Counter Styles. Do these cover your needs? Are the details correct? Are there other aspects related to counters and lists that need to be addressed? See available information or check for currently needed data.

GitHub issue #178

Customisable counters are needed for many languages.

There is no way for users to create local counter styles that are not built in to the browser, and users also often want to tweak the counter style in some way (esp. the prefix/suffix).

For Japanese, this means that a number of predefined counter styles in the CSS Counter Styles spec are not widely supported by browsers, or use a different separator from that specified. Because the custom mechanism of the Counter Styles spec is not supported by browsers other than Firefox, users are unable to fix this for themselves.

For more details, see this GitHub issue, which is being used to track this gap.

The following are additional items of Japanese-specific information.

Tests & results: i18n test suite, Basic tests for support of @counter-styles i18n test suite, Tests for hiragana/katakana styles i18n test suite, Tests for kanji character styles

Browser bug reports:

Chromium WebKit

GitHub issue #170

This issue is applicable to Chinese, Japanese, Korean, and Mongolian.

A common way to orient counters for lists in vertical text is to have an upright number with a dot alongside it. Alternatively, upright circled digits may be used.

vertical-lists

This is very common in printed material, but is not well supported in web pages.

Specs: css-pseudo The ::marker pseudo-element represents the automatically generated marker box of a list item, and can be styled.

The expected way to achieve this in HTML would be to use the following CSS: li::marker { text-combine-upright: all; }, however not all browsers support text-combine-upright.

Gecko and Blink based browsers now both support custom-defined counter styles. Webkit browsers do not.

Browser bug reports: Chromium Webkit Webkit Mozilla

Does the browser or ereader correctly handle special styling of the initial letter of a line or paragraph, such as for drop caps or similar? How about the size relationship between the large letter and the lines alongide? where does the large letter anchor relative to the lines alongside? is it normal to include initial quote marks in the large letter? is the large letter really a syllable? etc. Are all of these things working as expected? See available information or check for currently needed data.

Japanese Gap Analysis

Abstract

Status of This Document

1. Introduction

1.1 Work flow

1.2 Prioritization

2. Text direction

2.1 Vertical text

#180 Exceptional positioning of ideographic comma and katakana middle dot in vertical text

#171 Table cells don't handle vertical direction properly

#170 Unable to make list counters stand upright in vertical text

#169 Tate-chu-yoko lacks support for digits value

#168 Upright text orientation not supported

#167 Poor level of support for vertical form controls

2.2 Bidirectional text

3. Characters and phrases

3.1 Characters & encoding

3.2 Fonts

3.3 Font styles, weight, etc

3.4 Glyph shaping and positioning

#182 Positioning of opening brackets at line head

#181 Positioning of consecutive opening brackets, closing brackets, commas, full stops and middle dots

3.5 Cursive text

3.6 Baselines, line-height, etc

3.7 Transforming characters

#172 Japanese full-width transforms don't work

3.8 Grapheme/word segmentation & selection

3.9 Inline features & punctuation

3.10 Text decoration

#368 Emphasis dots should be centre-aligned with the text after the letter spacing is increased

#338 Additional aspects of handling boten marks

The Gap:

Tests & results:

Spec status:

Action taken:

Outcomes

Priority:

#173 Boten marks lack wide support

3.11 Quotations

#174 q element produces incorrect quotation marks when language changes

3.12 Inline notes & annotations

#318 Warichu cutting note not supported

#255 In-page search fails on ruby-annotated text

#177 Ruby alignment and other styling unavailable

#176 Double-sided ruby not displayed correctly

#175 Tabular markup not supported for ruby

3.13 Data formats & numbers

4. Lines and Paragraphs

4.1 Line breaking

4.2 Hyphenation

4.3 Text alignment & justification

4.4 Letter spacing

#312 Lack of support for applying extra spacing between Japanese and Western text

#265 Browsers apply extraneous spaces when letter-spacing

4.5 Lists, counters, etc.

#178 Local counter styles not supported

#170 Unable to make list counters stand upright in vertical text

4.6 Styling initials

5. Page & book layout

5.1 General page layout & progression

#171 Table cells don't handle vertical direction properly

5.2 Footnotes, endnotes, etc.

5.3 Page headers, footers, etc.

5.4 Forms & user interaction

#167 Poor level of support for vertical form controls

6. Other

6.1 Culture-specific features

6.2 What else?