It would be useful to be able to control the direction in which 'italicised' or 'oblique' text slants, since it may need to slant to the left.
` }, +'glyphs': { 'status':'advanced', "comments": `It would be useful to be able to control the height of diacritics relative to the base consonant for advanced typographic control.
` }, +'cursive': { 'status':'basic', "comments": `Various changes in styling currently break cursive connections. This should not happen. (Add details)
` }, +'boundaries': { 'status':'ok', "comments": `` }, +'quotations': { 'status':'basic', "comments": `In HTML and CSS the styling applied to nested multilingual quotations when using the q element chooses quotation marks based on the language of the text inside the quotation, rather than outside.
` }, +'numbers': { 'status':'', "comments": `Not yet clear whether there are issues related to the handling of arabic and eastern arabic script digits.
` }, +'transforms': { 'status':'na', "comments": `` }, +'spacing': { 'status':'basic', "comments": `It is very common in Arabic script to stretch words or phrases to a particular width (eg. to match a Latin translation or transcription above or below). This is achieved by lengthening the connections between letters, and to some extent by use of wide glyph variants, etc. The rules for which part of the text to stretch and how far are complicated - this is not the even spacing that usually occurs in tracked Latin text. There are currently no mechanisms for managing this process effectively in HTML/CSS.
` }, +'ruby': { 'status':'na', "comments": `` }, +'textdecoration': { 'status':'basic', "comments": `It must be possible to position under- and overlines further away from the baseline than for Latin text. There is not currently a way to achieve effective underlining in a way that works with the Arabic script.
` }, +'emphasis': { 'status':'ok', "comments": `` }, +'bidi': { 'status':'basic', "comments": `Edge still doesn't support directional isolation.
+There are questions about how to transmit information about the expected directional behaviour of certain strings.
+RLI, LRI, etc are still not well supported.
+....
` }, +'otherinline': { 'status':'', "comments": `` }, + +'linebreak': { 'status':'ok', "comments": `` }, +'hyphenation': { 'status':'na', "comments": `No hyphenation is used for Arabic when used with Arabic and Persian languages.
` }, +'justification': { 'status':'advanced', "comments": `Arabic script text uses various strategies for justification, which are different from say Latin script text. CSS doesn't provide any way to manage most of these behaviours. [Not sure whether to mark this a basic or advanced issue.]
` }, +'counters': { 'status':'basic', "comments": `Arabic script text uses local counter styles. While some of these are supported by some browsers, the set of symbols used and their order varies by language. Custom counter styles can be created using Firefox only. The CSS spec needs to become a Rec and more browsers need to support it.
` }, +'initialletter': { 'status':'advanced', "comments": `The parameters for managing initial-letter styling for the Arabic script are not well understood by the technology (for example, how to manage cursiveness across the boundary).
` }, +'baselines': { 'status':'ok', "comments": `` }, +'whitespace': { 'status':'na', "comments": `` }, +'otherpara': { 'status':'', "comments": `` }, + +'bidilayout': { 'status':'basic', "comments": `There needs to be wider adoption of logical keywords such as start and end, rather than left and right.
` }, +'vertical': { 'status':'na', "comments": `[We need to clarify whether there is a particular requirement for handling arabic text specially in vertical lines, such as upright glyphs.] [We are also waiting on implementation of sideways values of writing-modes in order to be able to effectively use arabic text in vertical arrangements (such as book spines, table headings, etc), but that is not a problem specific to arabic.]
` }, +'notes': { 'status':'', "comments": `` }, +'pageheaders': { 'status':'', "comments": `` }, +'otherpage': { 'status':'', "comments": `` }, + +'culture': { 'status':'', "comments": `` }, +'other': { 'status':'', "comments": `` }, + +} \ No newline at end of file diff --git a/gap-analysis/java-jv.js b/gap-analysis/java-jv.js new file mode 100644 index 0000000..a0bce4e --- /dev/null +++ b/gap-analysis/java-jv.js @@ -0,0 +1,40 @@ +var doctitle = "Arabic & Persian for HTML/CSS (Draft)" + +var compilers = "r12a" + +var report = { + +'encoding': { 'status':'ok', "comments": `` }, +'fontstyle': { 'status':'ok', "comments": `` }, +'glyphs': { 'status':'na', "comments": `` }, +'cursive': { 'status':'na', "comments": `` }, +'boundaries': { 'status':'basic', "comments": `Double-clicking highlights too much text.
` }, +'quotations': { 'status':'baoksic', "comments": `` }, +'numbers': { 'status':'ok', "comments": `` }, +'transforms': { 'status':'', "comments": `` }, +'spacing': { 'status':'na', "comments": `.
` }, +'ruby': { 'status':'na', "comments": `` }, +'textdecoration': { 'status':'na', "comments": `` }, +'emphasis': { 'status':'ok', "comments": `` }, +'bidi': { 'status':'na', "comments": `` }, +'otherinline': { 'status':'', "comments": `` }, + +'linebreak': { 'status':'broken', "comments": `Browsers don't wrap text. Wrapping needs to occur at orthographic syllable boundaries, which are not delimited by punctuation or spaces. Unlike Thai, which uses dictionary lookup to wrap word-by-word, the basic break points in Javanese can be calculated using a grammar for syllables. (There are likely to be additional considerations to check related to punctuation, digits, etc.)
` }, +'hyphenation': { 'status':'na', "comments": `There is a feature in use in print sometimes were when a line starts with ◌ꦺ [U+A9BA JAVANESE VOWEL SIGN TALING] another one is put at the end of the previous line. However, it is not felt that this is an important feature to enable at this time.
` }, +'justification': { 'status':'', "comments": `Currently no stretching is applied to a line in order to justify both edges, but it's not clear whether that is a requirement for Javanese anyway.
` }, +'counters': { 'status':'', "comments": `` }, +'initialletter': { 'status':'', "comments": `` }, +'baselines': { 'status':'ok', "comments": `` }, +'whitespace': { 'status':'na', "comments": `` }, +'otherpara': { 'status':'', "comments": `` }, + +'bidilayout': { 'status':'na', "comments": `` }, +'vertical': { 'status':'na', "comments": `` }, +'notes': { 'status':'', "comments": `` }, +'pageheaders': { 'status':'', "comments": `` }, +'otherpage': { 'status':'', "comments": `` }, + +'culture': { 'status':'', "comments": `` }, +'other': { 'status':'', "comments": `` }, + +} \ No newline at end of file diff --git a/gap-analysis/zh.js b/gap-analysis/zh.js index b9ac940..77adda1 100644 --- a/gap-analysis/zh.js +++ b/gap-analysis/zh.js @@ -16,8 +16,8 @@ var report = { 'ruby': { 'status':'advanced', "comments": `` }, 'textdecoration': { 'status':'advanced', "comments": `` }, 'emphasis': { 'status':'ok', "comments": `` }, -'inlinenotes': { 'status':'advanced', "comments": `Support needed for Inline Cutting Note (Warichu).
` }, 'bidi': { 'status':'na', "comments": `` }, +'otherinline': { 'status':'advanced', "comments": `Support needed for Inline Cutting Note (Warichu).
` }, 'linebreak': { 'status':'advanced', "comments": `` }, 'hyphenation': { 'status':'ok', "comments": `Chinese characters don't use hyphenation, but pinyin might use it.
` }, @@ -33,7 +33,7 @@ var report = { 'notes': { 'status':'advanced', "comments": `` }, 'pageheaders': { 'status':'', "comments": `We're not quite familiar with specifications like CSS Fragmentation, CSS Generated Content for Paged Media, or CSS Paged Media, so we need help from the CSS Working Group and the publishing WG/IG/BG/CGs.
We mark it as "unknown" for now.
` }, -'morepage': { 'status':'', "comments": `` }, +'otherpage': { 'status':'', "comments": `` }, 'culture': { 'status':'', "comments": `` }, 'other': { 'status':'', "comments": `` },