Some links on this page point to repositories or pages to which information will be added over time. Initially, the link may produce no results, but as issues, tests, etc. are created they will show up.
+ +Links that have a gray color led to no content the last time this document was updated. They are still live, however, since relevant content could be added at any time. When the document is updated, links that now point to results will have their live colour restored.
+The aim of this document is to describe the basic requirements for Kashmiri layout and text support on the Web and in eBooks when using the Perso-arabic script. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of Kashmiri.
+The aim of this document is to describe or point to the basic requirements for Kashmiri layout and text support on the Web and in eBooks when using the Perso-arabic script. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of Kashmiri.
The document focuses on typographic layout issues. For a deeper understanding of Kashmiri using the Arabic script and how it works see Kashmiri (Nastaliq Arabic) Orthography Notes, which includes topics such as: Phonology, Vowels, Consonants, Encoding choices, and Numbers.
+ +This document should contain no reference to a particular technology. For example, it should not say "CSS does/doesn't do such and such", and it should not describe how a technology, such as CSS, should implement the requirements. It is technology agnostic, so that it will be evergreen, and it simply describes how the script works. The gap analysis document is the appropriate place for all kinds of technology-specific information.
This document is pointed to by a separate document, Perso-arabic Kashmiri Gap Analysis, which describes gaps in support for Kashmiri on the Web, and prioritises and describes the impact of those gaps on the user.
- -Wherever an unsupported feature is identified through the gap analysis process, the requirements for that feature need to be documented. This document is where those requirements are described.
+This document should be used alongside a separate document, Perso-arabic Kashmiri Gap Analysis, which describes gaps in support for Kashmiri on the Web, and prioritises and describes the impact of those gaps on the user.
-This document should contain no reference to a particular technology. For example, it should not say "CSS does/doesn't do such and such", and it should not describe how a technology, such as CSS, should implement the requirements. It is technology agnostic, so that it will be evergreen, and it simply describes how the script works. The gap analysis document is the appropriate place for all kinds of technology-specific information.
+Gap reports are brought to the attention of spec and browser implementers, and are tracked via the Gap Analysis Pipeline. (Filter it for Kashmiri)
tbd
+ + + +