From ab5a0735bdfba826c91ef347139b6aed53e9a1c2 Mon Sep 17 00:00:00 2001 From: r12a Date: Tue, 19 Mar 2019 17:44:51 +0000 Subject: [PATCH] Redirects for Greek, Dutch & Hungarian gap analysis docs --- gap-analysis/docs/el-gap/index.html | 564 +--------------------------- gap-analysis/docs/latn-hu.html | 537 +------------------------- gap-analysis/docs/latn-nl.html | 545 +-------------------------- 3 files changed, 3 insertions(+), 1643 deletions(-) diff --git a/gap-analysis/docs/el-gap/index.html b/gap-analysis/docs/el-gap/index.html index c3275bf..aecbe94 100644 --- a/gap-analysis/docs/el-gap/index.html +++ b/gap-analysis/docs/el-gap/index.html @@ -1,573 +1,11 @@ - - Greek Gap Analysis - - - -
-

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

-

This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.

- - -
-

Sending comments on this document

- -

If you wish to make comments regarding this document, please raise them as github issues. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.

- -

To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on  using a URL.

-
-
- -
-

Introduction

-

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 by specifications or user agents (browsers, e-readers, etc.).

- -

A summary of this report and others can be found as part of the language matrix.

- -
-

Work flow

-

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.

- - -
- -
-

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 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.)

-
-
- - - - - -
-

Text direction

-

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

- -
-

Vertical text

-

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.

- - - -

-
- - - - -
-

Bidirectional text

-

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.

- - -

-
-
- - - - - -
-

Characters and phrases

- - - -
-

Characters & encoding

-

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?

- -

-
- - - -
-

Fonts

-

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.

- -

-
- - - -
-

Font styles, weight, etc

-

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.

- - -

-
- - - -
-

Glyph shaping and positioning

-

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.

- - - -

-
- - - -
-

Cursive text

-

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.

- - -

-
- - - -
-

Transforming characters

-

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.

- -

There are tests available in the i18n test suite:

- -

The upper/lowercase tests show that Firefox, Chrome, and Safari fail the uppercase test for characters that are expected to have a form similar to ῼ. It produces instead ΩΙ, which is the form obtained by decomposing the character first, then applying uppercase.

-

The special casing tests show that, on the whole, Firefox, Chrome and Safari will uppercase Greek specials as described in Unicode's SpecialCasing.txt (Safari fails on one character, Ϊ́̈). Edge, however, fails these tests.

-

Only Firefox and Chrome pass all the tailoring tests. Failures for Safari and Edge include the following:

-
    -
  1. transform: uppercase doesn't cause Greek words that are all uppercase to lose tonos
    2. -
  2. transform: uppercase doesn't cause Greek words that are all uppercase to convert tonos plus dialytika to just dialytika, and convert diphthongs with tonos on the first character to a dialytika on the second character
    3. -
  3. text-transform: uppercase doesn't cause a disjunctive eta in a Greek sentence keeps its tonos diacritic.
    4. -
-
- - - - -
-

Text segmentation & selection

-

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.

- - -

-
- - - -
-

Text decoration

-

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.

- - -

-
- - - -
-

Quotations

-

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.

- - -
-

Default quotation marks for q element

-

If the html tag sets the language of a page, the HTML specification says that the q element should by default produce quotation marks according to the information in CLDR for that language.

-

For Greek, the default quote marks should be, reading right to left, «...», and embedded quote marks “...”. Firefox produces the default English quotes. Chrome & Safari are ok. Edge produces the outer quote marks as expected, but uses single quotes for the inner ones. See a test and results.

-
- -
-

Default quotation marks in a new language section

-

In addition, the default quotation marks for the q element are not set to the appropriate characters by the browser when the element appears inside a Greek section of a page that has a different overall language. This is currently per the HTML specification (both W3C and WhatWG). There is an issue raised against the WhatWG version for this to be changed.

-
- -
-

Embedded quotations in a different language

-

Greek quotes embedded in text in another language can also be problematic if the outer language uses different quotation marks. This is due to the browsers choosing default quotation marks based on the language of the quotation, rather than that of the surrounding text. See a test. This behaviour is specified in the WhatWG version of the HTML spec, but no longer in the W3C version. There is an issue raised against the WhatWG version for this to be changed.

-
- -

Marking all the above as advanced, because use of the q element is optional (quote characters can be used instead), and it can be styled using CSS for the general case.

-
- - - -
-

Inline notes & annotations

-

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.

- - -

-
- - - -
-

Numbers, dates, etc.

-

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)? See available information or check for currently needed data.

- - -

-
- - - -
-

Other inline features

-

Does the script have special ways of representing inline notes (such as kumimoji in Japanese) or other inline features that need to be supported? See available information or check for currently needed data.

- - -

-
- - - - - - - - -
-

Lines and Paragraphs

- - -
-

Line breaking

-

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.

- - -

-
- - - -
-

Hyphenation

-

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.

- - -

-
- - - -
-

Text alignment & justification

-

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.

- - -

-
- - - -
-

Word & letter spacing

-

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.

- - -

-
- - - -
-

Counters, lists, etc.

-

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.

- - -

Tests:

-
    -
  1. Simple alphabetic
    2. -
  2. Greek script
    3. -
-

The lower-greek counter style is defined in the CSS Counter Styles Level 3 specification, however the greek-lower-modern style described in Ready-made Counter Styles is more commonly used in Greece. CSS2.1 included the lower-greek keyword, and all major browsers support the lower-greek counter style but not the greek-lower-modern style.

-

The CSS Counter Styles spec allows users to create their own counter styles, but the feature is only implemented by Firefox at the moment.

-

Effectively, this means that there isn't a good greek counter style feature available for authors.

- -
- - - -
-

Styling initials

-

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.

- - -

-
- - - -
-

Baselines & inline alignment

-

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

- - -

-
- - - -
-

Other paragraph features

-

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.

- - -

-
- -
- - - - - - - -
-

Page & book layout

- -
-

General page layout & progression

-

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? See available information or check for currently needed data.

- - -

-
- - - -
-

Notes, footnotes, etc.

-

Does your script have special requirements for notes, 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.

- - -

-
- - - -
-

Page numbering, running headers, etc.

-

Are there special conventions for page numbering, or the way that running headers and the like are handled? See available information or check for currently needed data.

- - -

-
- - - -
-

Forms & user interaction

-

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.

- - -

-
- - - -
-

Other page layout & pagination features

-

Some cultures define text 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? If pages progress RTL, are there issues for support with paged media? What about things such as cross-references, bookmarks, columns, printer marks, tables of contents and indexes? See available information or check for currently needed data.

- - -

-
-
- - - - - - -
-

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?

- - -

-
- -
- - - - -
-Show summary -

-

-
-
-
-
-
+
This document is now available at https://w3c.github.io/eurlreq/gap-analysis/grek-gap

 
 
diff --git a/gap-analysis/docs/latn-hu.html b/gap-analysis/docs/latn-hu.html
index 366bed1..a047e87 100644
--- a/gap-analysis/docs/latn-hu.html
+++ b/gap-analysis/docs/latn-hu.html
@@ -1,546 +1,11 @@
 
-
 
 
   
-
   Hungarian Gap Analysis
-  
-  
-  
 
 
 
-  

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

-
This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.

-    
-
-    

-    
Sending comments on this document

-
-      
If you wish to make comments regarding this document, please raise them as github issues. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.

-
-      
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on  using a URL.

-    

-  

-
-  

-    
Introduction

-    
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 by specifications or user agents (browsers, e-readers, etc.). 

-
-    
A summary of this report and others can be found as part of the language matrix.

-    
-    

-    
Work flow

-    
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.

-    
-    
-    

-    
-    

-    
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 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.) 

-    

-

-    
-    
-    
-  
-    
-

-    
Text direction

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

-
-

-
Vertical text

-    
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.

-
-
-
-    
Vertical text may occur for special effects (the spine of a book, table column headings). Typographically, it is simply horizontal text that is rotated. The ‘writing-modes: sideways-lr/rl’ CSS feature should solve that, but isn't supported yet.

-

-
-
-
-
-

-    
Bidirectional text

-    
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.

-
-
-    

-

-

-
-
-
-
-
-

-
Characters and phrases

-    
-    
-    
-

-    
Characters & encoding

-    
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?

-
-    
The presence of a Hungarian specific diacritic (") means that ISO-8859-1 cannot be used; instead, ISO-8859-2 must be used (or UTF-8). In the early days of the Web this was not really well handled on Hungarian Web sites, and they usually used, for example, 'õ' instead of 'ő', even for texts like online newspapers. The problem seems to have disappeared by now with UTF-8 coming to the fore, although I still found a page doing that (oh irony! it is a page on Hungarian Grammar:-)

-    

-
-
-
-

-    
Fonts

-    
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.

-
-    

-

-
-
-
-

-    
Font  styles, weight, etc

-    
 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.

-
-
-    

-    

-
-
-
-

-    
Glyph shaping and positioning

-    
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.

-
-
-
-    

-    

-
-
-
-

-    
Cursive text

-    
 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.

-
-
-    

-    

-
-
-
-

-    
Transforming characters

-    
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.

-
-    
Hungarian has a number of digraphs, like 'gy', 'ty', 'sz', that refer to distinct, different sounds. However, the typography rules do not follow this: capitalization is "Gyomor", instead of "GYomor". Ie, they are not considered, typographically, as single letters (in contrast to the Dutch "ij"). Consequently the usual transformations work.

-
See also the section on initial letter styling.

-

-
-
-
-
-

-    
Text segmentation & selection

-    
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.

-
-
-    
 You might expect double click to select a word including any apostrophes ('s, 't, dia's). Some software does, some doesn't. Ditto for words with dashes (ex-voetballer, vice-voorzitter), but no software on or off the Web seems to do so.

-    

-    
-    
-    
-

-    
Text decoration

-    
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.

-
-
-    
 

-

-
-
-
-

-    
Quotations

-    
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.

-
-
-    
Hungarian uses the German-style quotations marks, e.g., „Jónapot”. When using the <q> element some browsers do it right (e.g., Chrome, Safari) but, e.g., Mozilla does not.

-

-
-
-
-

-    
Inline notes & annotations

-    
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.

-
-
-    

-    

-
-
-
-

-    
Numbers, dates, etc.

-    
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)? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Other inline features

-    
Does the script have special ways of representing inline notes (such as  kumimoji in Japanese) or other inline features that need to be supported? See available information or check for currently needed data.

-
-
-    

-    

-
-

-
-
-
-
-
-
-

-
Lines and Paragraphs

-
- 
-

-    
Line breaking

-    
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.

-
-
-    

-

-
-
-
-

-    
Hyphenation

-    
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.

-
-
-    
Few browsers so far support hyphenation. It works on FF (yay!) but it does not work on Chrome or Safari.

-
Hyphenation has some more complex rules (handling compound words, digraphs, rules on repeated letters expressing emphasis-like longer sounds, etc.). It would need a more systematic test to decide whether everything is fine on FF but, at first glance, it seems to be working fine. It does not use the break opportunities when digraphs are duplicated. E.g., in "Összeg" the "ssz" is a shortened form for "szsz", i.e., a double "sz" digraph; when hyphenating, one could do a "Ösz-szeg" which FF doesn't do. That being said, it is a bit of an edge case and people often do what FF does. I.e., I guess an "ok" status is fine for FF. But the non-existent hyphenation in other browsers means that the feature is still "advanced".

-

-
-
-
-

-    
Text alignment & justification

-    
 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.

-
-
-    
 The (rarely used) hanging punctuation is not supported. Some newspapers allow letter spacing to help with justification, which is not supported either.

-

-
-
-
-

-    
Word & letter spacing

-    
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.

-
-
-    

-

-
-
-
-

-    
Counters, lists, etc.

-    
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.

-
-
-    

-

-
-
-
-

-    
Styling initials

-    
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.

-
-
-    

-

-
-
-
-

-    
Baselines & inline alignment

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

-
-
-    

-

-
-
-
-

-    
Other paragraph features

-    
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.

-
-
-    

-

-
-

-
-
-
-
-
-
-
-

-
Page & book layout

-
-

-    
General page layout & progression

-    
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? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Notes, footnotes, etc.

-    
Does your script have special requirements for notes, 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.

-
-
-    

-    

-
-
-
-

-    
Page numbering, running headers, etc.

-    
Are there special conventions for page numbering, or the way that running headers and the like are handled? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Forms & user interaction

-    
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.

-
-
-    

-

-
-
-
-

-    
Other page layout & pagination features

-    
Some cultures define text 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? If pages progress RTL, are there issues for support with paged media? What about things such as cross-references, bookmarks, columns, printer marks,  tables of contents and indexes? See available information or check for currently needed data.

-
-
-    

-    

-

-
-
-
-
-
-
-

-
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?

-
-
-    
Some other characteristics of Hungarian (none of which pose problems on the Web): 

-
    
-
  • The rules for quotation marks and their nesting are similar to British English. However, punctuation is different: whereas in English one would put the full stop before the bracket like in "(A bracketed text.)", Hungarian does it the other way round like "(Zárójeles szöveg)." 
    • 
-
  • Text is typically way longer than equivalent English text and words are often much longer on average, too. 
    • 
-
  • Pronunciation is mostly easy to guess from the spelling. The other way round may be more complicated, because there are cases when the same sound can be written in different ways (e.g., "ly" and "j"), or because today's pronounciation tends to be less careful. This may be relevant for text-to-speech. 
    • 
-
  • Numbers use a space between thousands and a comma before the decimals. The ‘0’ before the comma cannot be omitted (‘0,5’ but not ‘,5’). 
    • 
-
  • Negative numbers start with a minus or dash.
    • 
-
  • The currency symbol is used after the amount (10Ft). 
    • 
-
  • There is no space before punctuation ("akkor,", "mondta:", "rendben van!"). 
    • 
-
  • There is a simple space after the full stop at the end of a sentence. 
    • 
-
  • When text on the spine of a book is rotated, it is always in such a way that the book can lie with the back cover on top (i.e., like in French but different from English). 
    • 
-
  • The language uses a fair number of diacritics; one of those, used on the letters 'o' and 'u', is, afaik, specific to Hungarian: 'ő' and 'ű' (and their capitalized counterpart). Diacritics are important for the meaning of the words, and cannot be ommitted or replaced even when capitalized (in contrast to French which usually drops diacritics for capital letters): e.g., "Álom" means "Dream", whereas "Alom" means "Litter". 
    • 
-
  • An i18n issue for Hungarian is the fact that Hungarian names are in reverse order compared to all other European languages: it is family name followed by surname. I.e., it is "Herman Iván", and not "Iván Herman". (This is the same as for a number of Asian languages, afaik.) This means that Web forms using the term "first name" and "last name" are the source of endless confusions for Hungarians. 
    • 
-
  • Although I presume this is more a matter for Unicode, for the sorting order digraphs are considered to be different letters; in the order of letters, the digraph immediately follows the first letter. I.e., "c"  is followed by "cs" and is before the "d" in the ABC, and the word “cukor” (sugar) precedes the word “csupor” (mug) in a dictionary, because "cs" is a digraph. 
    • 
-

-    

-    
-

-
-
-
-
-

-Show summary
-

-

-
-
-
-
-
-
+
This document is now available at https://w3c.github.io/eurlreq/gap-analysis/latn-hu-gap

 
 
diff --git a/gap-analysis/docs/latn-nl.html b/gap-analysis/docs/latn-nl.html
index 42442cb..3419a88 100644
--- a/gap-analysis/docs/latn-nl.html
+++ b/gap-analysis/docs/latn-nl.html
@@ -1,554 +1,11 @@
 
-
 
 
   
-
   Dutch Gap Analysis
-  
-  
-  
 
 
 
-  

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

-
This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.

-

-    
-
-    

-    
Sending comments on this document

-
-      
If you wish to make comments regarding this document, please raise them as github issues. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.

-
-      
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on  using a URL.

-    

-  

-
-  

-    
Introduction

-    
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 by specifications or user agents (browsers, e-readers, etc.). 

-
-    
A summary of this report and others can be found as part of the language matrix.

-    
-    

-    
Work flow

-    
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.

-    
-    
-    

-    
-    

-    
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 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.) 

-    

-

-    
-    
-    
-
-    
-    
-    
-

-    
Text direction

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

-
-

-
Vertical text

-    
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.

-
-
-
-    
 Vertical text may occur for special effects (the spine of a book, table column headings). Typographically, it is simply horizontal text that is rotated. The ‘writing-modes: sideways-lr/rl’ CSS feature should solve that, but isn't supported yet. 

-

-
-
-
-
-

-    
Bidirectional text

-    
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.

-
-
-    

-

-

-
-
-
-
-
-

-
Characters and phrases

-    
-    
-    
-

-    
Characters & encoding

-    
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?

-
-    

-    

-
-
-
-

-    
Fonts

-    
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.

-
-    

-

-
-
-
-

-    
Font  styles, weight, etc

-    
 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.

-
-
-    

-    

-
-
-
-

-    
Glyph shaping and positioning

-    
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.

-
-
-
-    

-    

-
-
-
-

-    
Cursive text

-    
 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.

-
-
-    

-    

-
-
-
-

-    
Transforming characters

-    
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.

-
-    
Capitalisation doesn't convert ij at the start of a word to IJ in most browsers, even if the text is labelled as Dutch. See test results at https://www.w3.org/International/tests/repo/results/text-transform#dutch_tailoring 

-
See also the section on initial letter styling.

-

-
-
-
-
-

-    
Text segmentation & selection

-    
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.

-
-
-    

-    

-    
-    
-    
-

-    
Text decoration

-    
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.

-
-
-    
Assumed same as for Latin.

-

-
-
-
-

-    
Quotations

-    
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.

-
-
-    
 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.

-

-
-
-
-

-    
Inline notes & annotations

-    
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.

-
-
-    

-    

-
-
-
-

-    
Numbers, dates, etc.

-    
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)? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Other inline features

-    
Does the script have special ways of representing inline notes (such as  kumimoji in Japanese) or other inline features that need to be supported? See available information or check for currently needed data.

-
-
-    

-    

-
-

-
-
-
-
-
-
-

-
Lines and Paragraphs

-
- 
-

-    
Line breaking

-    
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.

-
-
-    
 But see hyphenation below. 

-

-
-
-
-

-    
Hyphenation

-    
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.

-
-
-    
 Few browsers so far support hyphenation. When they do, they break correctly in most cases (better on Debian Linux than on Mac OS X, it seems), but they do not use the break opportunities where breaking would cause letters to change (cafeetje → café-tje, autootje → auto-tje) or they do it wrong (skiërs → ski-ers, not ski-ërs). 

-

-
-
-
-

-    
Text alignment & justification

-    
 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.

-
-
-    
 The (rarely used) hanging punctuation is not supported. Some newspapers allow letter spacing to help with justification, which is not supported either.

-

-
-
-
-

-    
Word & letter spacing

-    
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.

-
-
-    
 Current implementations put the letter spacing after a letter even when it is at the end of a line, which makes the line look misaligned in justified or right-justified text. 

-

-
-
-
-

-    
Counters, lists, etc.

-    
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.

-
-
-    

-

-
-
-
-

-    
Styling initials

-    
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.

-
-
-    
 Despite the CSS specification specifically mentioning that the IJ combination should be treated as a single letter, browser don't seem to support this. 

-

-
-
-
-

-    
Baselines & inline alignment

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

-
-
-    

-

-
-
-
-

-    
Other paragraph features

-    
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.

-
-
-    

-

-
-

-
-
-
-
-
-
-
-

-
Page & book layout

-
-

-    
General page layout & progression

-    
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? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Notes, footnotes, etc.

-    
Does your script have special requirements for notes, 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.

-
-
-    

-    

-
-
-
-

-    
Page numbering, running headers, etc.

-    
Are there special conventions for page numbering, or the way that running headers and the like are handled? See available information or check for currently needed data.

-
-
-    

-    

-
-
-
-

-    
Forms & user interaction

-    
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.

-
-
-    

-

-
-
-
-

-    
Other page layout & pagination features

-    
Some cultures define text 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? If pages progress RTL, are there issues for support with paged media? What about things such as cross-references, bookmarks, columns, printer marks,  tables of contents and indexes? See available information or check for currently needed data.

-
-
-    

-    

-

-
-
-
-
-
-
-

-
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).

-
-
-    
The ‘ij’ is for some purposes a single letter, the 25th letter of the alphabet. The ‘y’, called ‘Griekse ij’ (Greek y), is not in the alphabet that children learn, although there are many (imported) words and names that use it. In handwriting and in some children's books, the ‘ij’ is a single glyph. (Never written as ÿ, but looking like a ü with the tail of a j or a sans-serif g. Children quickly learn that the ij is written as i+j in books and on the computer, but most people continue to write a single glyph when they write by hand. Dictionaries and alphabetical indexes usually sort ij with i, but some put ij after x. But when capitalizing a word that begins wih ij, both letters are always capitalized: ijs → IJs (meaning ‘ice’). 

-
The special hyphenation rules are explained above. 

-
Some other characteristics of Dutch (none of which pose problems on the Web):

-
    
-
  • There are official rules for formatting postal codes in addresses (‘1000 AA AMSTERDAM’). 
    • 
-
  • There is a traditional way to layout (business) letters. 
    • 
-
  • The rules for quotation marks and their nesting are similar to British English. (But punctuation and quotation marks may swap place compared to American English.) 
    • 
-
  • Text is typically slightly longer than equivalent English text and words are slightly longer on average, too. 
    • 
-
  • Pronunciation is usually easy to guess from the spelling. (The other way round is not so easy, because many combinations sound the same: au = ou, dt = t, ei = ij, heetten = heten, etc.). 
    • 
-
  • Certain words (mostly names and words derived from names) are capitalized. 
    • 
-
  • Numbers use a dot between thousands and a comma before the decimals. The ‘0’ before the comma cannot be omitted (‘0,5’ but not ‘,5’). 
    • 
-
  • Negative numbers start with a minus or dash. 
    • 
-
  • The currency symbol precedes the amount (€10). 
    • 
-
  • Ordinal numbers consist of digits followed by either an ‘e’ or one of ‘de’/‘ste’, in the same size and style as the digits: 1e, 2e, 100e or: 1ste, 2de, 100ste. 
    • 
-
  • There is no space before punctuation (‘dan,’, ‘zei:’, ‘goed!’). 
    • 
-
  • There is a simple space after the full stop at the end of a sentence. 
    • 
-
  • The page numbered 1 in a book is a right hand page. 
    • 
-
  • When text on the spine of a book is rotated, it is always in such a way that the book can lie with the front cover on top (i.e., like in English but different from French). 
    • 
-
  • Some diacritics are used: diaeresis to indicate otherwise ambiguous syllable breaks (‘geërft’, two syllables vs ‘geeft’, one syllable), acute and grave accents for emphasis or French loan words (‘hé!’ ‘één’, ‘café‘), cedilla for loan words (Curaçao, reçu). 
    • 
-

-    

-
-
-
-

-    
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?

-
-
-    

-    

-    
-

-
-
-
-
-

-Show summary
-

-

-
-
-
-
-
-
+
This document is now available at https://w3c.github.io/eurlreq/gap-analysis/latn-nl-gap