| CARVIEW |
This document describes and prioritises gaps for the support of the Javanese script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, such as HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
This document describes and prioritises gaps for the support of the Javanese script 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. 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 in the GitHub repository Southeast Asian Language Enablement (sealreq), with contributors from the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.
Contributors
The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.
See also the GitHub contributors list for the Southeast Asian Language Enablement project, and the discussions related to the Javanese script.
About this 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 that people encounter when trying to use languages written in the Javanese 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.
Prioritization
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 feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.
A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines.
Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may 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 will be the lowest denominator.
Related documents
A summary of this report and others can be found as part of the Language Matrix.
Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. Find the Javanese items.
For more information about the Javanese script, including requirements, tests, GitHub discussions, type samples, and more, see Javanese Script Resources.
Text direction
See also General page layout & progression for features such as column layout, page turning direction, etc. that are affected by text direction.
Writing mode
Bidirectional text
Glyph shaping & positioning
Fonts & font styles
Context-based shaping and positioning
Letterform slopes, weights, & italics
Cursive text
Case & other character transforms
Typographic units
Characters & encoding
Grapheme/word segmentation & selection
Punctuation & inline features
Phrase & section boundaries
Quotations & citations
Emphasis & highlighting
Abbreviation, ellipsis & repetition
Inline notes & annotations
Text decoration & other inline features
Data formats & numbers
Line and paragraph layout
Line breaking & hyphenation
Text alignment & justification
Text spacing
Baselines, line-height, etc
Lists, counters, etc.
Styling initials
Page & book layout
General page layout & progression
Grids & tables
Footnotes, endnotes, etc.
Page headers, footers, etc.
Forms & user interaction
Other
Culture-specific features
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).
What else?
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?