Copyright © 2018-2021 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.
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.
This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
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 document complements the document Text Layout Requirements for the Japanese Script, which describes the requirements for areas where gaps appear. It is linked to from the language matrix that tracks Web support for many languages.
The editor's draft of this document is being developed by the Japanese Layout Task Force, part of the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.
This document was published by the Internationalization Working Group as a Working Draft using the Recommendation track.
Publication as a Working Draft does not imply endorsement by W3C and its Members.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is governed by the 2 November 2021 W3C Process Document.
The W3C needs to make sure that the needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.
This page documents difficulties people encounter when trying to use the Japanese language and script on the Web.
Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.
A summary of this report and others can be found as part of the language matrix.
This version of the document is a preliminary analysis
Gap analysis work usually starts with a preliminary analysis, conducted quickly by one or a small group of experts. Then a more detailed analysis is carried out, involving a wider range of experts. The detailed analysis may involve the development of tests, in order to illustrate issues and track results for browsers. The next phase is ongoing maintenance. It is expected that the resulting document will not be frozen: as gaps are fixed, this should be noted in the document. It is also possible that new gaps are noticed or arise, and they can be added to this document when that happens.
As the gap analysis develops, the requirements for features that are problematic should be described in the companion document, Japanese Layout Requirements. Links to the appropriate part of that document should be added to this document as the material is created. Note that the requirements document should not contain any technology-specific information: all of that belongs here.
This document not only describes gaps, it also attempts to prioritise them in terms of the impact on the local user. The prioritisation is indicated by colour.
Key:
It is important to note that these colours do not indicate to what extent a particular features is broken. They indicate the impact of a broken or missing feature on the content author or end user.
Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.
The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide. If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section should be the lowest denominator.
A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.)
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.
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.
There is a related discussion about how to achieve this.
Tests & results: interactive test
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 to td
produces the expected directionality
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
There are tests for boten mark support that show that they are not supported by Chrome 63.0.3239.132 or Edge, but they are supported by Firefox 58.0 and Safari 11.0.3.
The expected behaviour for basic support of boten marks is specified in CSS.
Given that there are alternative ways of showing emphasis, and although there are already two implementations, I mark this as an advanced need.
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:
JLReq also requires that emphasis marks not appear over commas, full stops and brackets.
There are currently no tests for these behaviours, and no requirements in jlreq for the former (with ruby). Need to take a closer look.
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.
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.
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.
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.
Tests & results:
Interactive test, In page search will find text that has ruby annotations in interleaved markup
Gecko, Blink, and Webkit browsers all fail to recognise strings when they have ruby text.
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.
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.
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.
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.
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.
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.
This issue is described in more detail and tracked here.
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.
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:
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.
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.
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.
How are the main text area and ancilliary areas positioned and defined? Are there any special requirements here, such as dimensions in characters for the Japanese kihon hanmen? The book cover for scripts that are read right-to-left scripts is on the right of the spine, rather than the left. Is that provided for? When content can flow vertically and to the left or right, how do you specify the location of objects, text, etc. relative to the flow? For example, keywords 'left' and 'right' are likely to need to be reversed for pages written in English and page written in Arabic. Do tables and grid layouts work as expected? How do columns work in vertical text? Can you mix block of vertical and horizontal text correctly? Does text scroll in the expected direction? Other topics that belong here include any local requirements for things such as printer marks, tables of contents and indexes. See available information or check for currently needed data.
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 to td
produces the expected directionality
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.
Does your script have special requirements for footnotes, endnotes or other necessary annotations of this kind in the way needed for your culture? (There is a section above for purely inline annotations, such as ruby or warichu. This section is more about annotation systems that separate the reference marks and the content of the notes.) See available information or check for currently needed data.
Are vertical form controls well supported? In right-to-left scripts, is it possible to set the base direction for a form field? Is the scroll bar on the correct side? etc. See available information or check for currently needed data.
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.
Sometimes a script or language does things that are not common outside of its sphere of influence. This is a loose bag of additional items that weren't previously mentioned. This section may also be relevant for observations related to locale formats (such as number, date, currency, format support).
There are many other CSS modules which may need review for script-specific requirements, not to mention the SVG, HTML, Speech, MathML and other specifications. What else is likely to cause problems for worldwide deployment of the Web, and what requirements need to be addressed to make the Web function well locally?