Gap analysis checklist
Language & script X for HTML/CSS
The W3C needs to make sure that the text layout and typographic 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 issues for a given script or language in terms of support in specifications or user agents. If you want to raise an issue or comment against this page, use the github issues list.
A summary of this report and others can be found as part of a matrix in the overview page.
Each section starts with a prompt in italicised text, intended to help you think of things that might be addressed in that section. When summarising the situation, try to indicate which languages you are covering with your text. Use clear signposting where there are divergent issues related to specific languages.
status to one of the following, which indicates the impact of the missing features on the ability to use the language on the Web (ie. if a feature is unavailable the appropriate label isn't necessarily 'broken', the label assigned depends on the importance of that feature to using the language on the Web).
- ok (no problems)
- na (not applicable)
- advanced (work needed to support advanced applications, such as fine quality book production)
- basic (work is needed to support styling for basic/common web page use in this language)
- broken (work needed to enable interoperable semantics, or basic display on the Web that prevents effective use of the Web for this language).
This report was compiled by:
Are there any character repertoire issues preventing use of this script on the Web? Do variation selectors need attention?
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.
Does this script require additional work to support altering 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? 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.
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? See available information or check for currently needed data.
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? Are there issues when applying punctuation than could be fixed by the application? See available information or check for currently needed data.
Many scripts create emphasis or other effects by spacing out the letters or syllables in a word. We know there are questions here about how this should work in Indic and SE Asian scripts, and in Arabic-based scripts. Are there requirements for other scripts that we should add? (For justification related spacing, see below.) See available information or check for currently needed data.
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? See available information or check for currently needed data.
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.
Bold and italic are not always appropriate for expressing emphasis, and some scripts have their own unique ways of doing it, that are not in the Western tradition at all. Does this script require support for emphasising or highlighting text that cannot be achieved currently? See available information or check for currently needed data.
Does your script have special ways of representing inline notes (such as wakiten or kumimoji in Japanese) or other inline features that need to be supported? 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? What characters should not appear at the end or start of a line, and what should be done to prevent that? Does line-breaking wrap whole 'words' at a time, or characters, or something else (such as syllables in Tibetan)? 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? See available information or check for currently needed data.
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. Are the details correct? We have another document that provides over 120 templates for user-defined counter styles in over 30 scripts. Are there more? Are there other aspects related to counters and lists that need to be addressed? See available information or check for currently needed data.
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?
See available information or check for currently needed data.
Do the rules for transforming white space in the source text for display meet the requirements of your script? This is particularly relevant for Far Eastern and South East Asian scripts, that don't use spaces between words.
In your script, is the first line of text typically indented at the start of a paragraph? Are there other features of paragraph design that are peculiar to your script? See available information or check for currently needed data.
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. See available information or check for currently needed data.
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.
Does your script have special requirements for notes, footnotes, endnotes or other necessary annotations of this kind in the way needed for your culture? See available information or check for currently needed data.
Other page layout and pagination features
Some cultures define page areas and page progression direction very differently from those in the West (eg. kihon hanmen in Japanese). Is this an issue for you? Are widows and orphans relevant? In what order do pages progress, RTL or LTR? See available information or check for currently needed data.
Sometimes a script or language does things that are not common outside of it 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?
If you have comments about this page, send them to firstname.lastname@example.org.
Content last changed 2017-10-06 15:03 GMT
Copyright © 2017 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.