Skip to content

Commit 0c260c2

Browse files
r12ar12a
committed
gap-analysis/gujr-gap Update front matter
1 parent 1f3c776 commit 0c260c2

File tree

1 file changed

+55
-50
lines changed

1 file changed

+55
-50
lines changed

‎gap-analysis/gujr-gap.html

+55-50
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,12 @@
1414
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
1515
specStatus: "ED",
1616
//publishDate: "2020-06-16",
17-
//previousPublishDate: "2014-12-16",
18-
//previousMaturity: "FPWD",
1917

2018
noRecTrack: true,
2119
shortName: "gujr-gap",
2220
copyrightStart: "2018",
2321
edDraftURI: "https://w3c.github.io/iip/gap-analysis/gujr-gap",
2422

25-
// if this is a LCWD, uncomment and set the end of its review period
26-
// lcEnd: "2009-08-05",
27-
2823
// editors, add as many as you like
2924
// only "name" is required
3025
editors: [
@@ -67,15 +62,16 @@
6762
</head>
6863

6964
<body>
70-
<div id="abstract">
71-
<p>This document describes and prioritises gaps for the support of languages using the Gujarati 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. <strong>This is a preliminary analysis.</strong></p>
72-
</div>
73-
74-
<div id="sotd">
75-
<p>This document describes and prioritises gaps for the support of languages using the Gujarati 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. This document
76-
<!--complements the document <a href="https://w3c.github.io/xxxx/"> Xxxx Layout Requirements</a>, which describes the requirements for areas where gaps appear. It is-->
77-
linked to from the <a href="https://w3c.github.io/typography/gap-analysis/language-matrix.html">language matrix</a> that tracks Web support for many languages.</p>
78-
<p>The editor's draft of this document is being developed by the <a href="https://w3c.github.io/iip/">India International Program Layout Task Force</a>, part of the W3C <a href="https://www.w3.org/International/ig/">Internationalization Interest Group</a>. It is published by the <a href="https://www.w3.org/International/core/">Internationalization Working Group</a>. The end target for this document is a Working Group Note.</p>
65+
<div id="abstract">
66+
<p>This document describes and prioritises gaps for the support of the Gujarati 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.</p>
67+
</div>
68+
69+
70+
<div id="sotd">
71+
<p>This document describes and prioritises gaps for the support of the Gujarati 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.
72+
It is linked to from the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html">language matrix</a> that tracks Web support for many languages.</p>
73+
74+
<p>The editor's draft of this document is being developed in the GitHub repository <a href="https://w3c.github.io/iip/home">Indian Language Enablement (ilreq)</a>, with contributors from the <abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/International/i18n-activity/i18n-ig/">Internationalization Interest Group</a>. It is published by the <a href="https://www.w3.org/International/i18n-activity/i18n-wg/">Internationalization Working Group</a>. The end target for this document is a Working Group Note.</p>
7975
</div>
8076

8177

@@ -86,20 +82,21 @@
8682

8783

8884

85+
86+
87+
8988
<section id="h_introduction">
9089
<h2>Introduction</h2>
9190

9291

9392
<section id="contributors">
9493
<h2>Contributors</h2>
9594

96-
<p>The original version of this document was created by Neha Gupta (C-DAC). It was extended by Richard Ishida.</p>
95+
<p>This document was created by Richard Ishida.</p>
9796
<!--
98-
<p>Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).</p>
99-
100-
<p class="acknowledgement">This Person, That Person, etc</p>
97+
<p>The following people contributed information to the gap reports in this document (in alphabetic order): This Person, That Person, etc</p>
10198
-->
102-
<p data-lang="en">Other contributors can be found in the <a href="https://github.com/w3c/iip/graphs/contributors">GitHub contributors list</a>.</p>
99+
<p data-lang="en">See also the <a href="https://github.com/w3c/iip/graphs/contributors">GitHub contributors list</a> for the Indian Language Enablement project, and the <a href="https://github.com/w3c/iip/issues?q=is%3Aissue+label%3As%3Agujr">discussions related to the Gujarati script</a>.</p>
103100
</section>
104101

105102

@@ -112,53 +109,61 @@ <h2>About this document</h2>
112109

113110
<p>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.</p>
114111

115-
<p>This page documents difficulties people encounter when trying to use the Gujarati language in the Gujarati script on the Web. </p>
112+
<p>This page documents difficulties that people encounter when trying to use languages written in the Gujarati script on the Web.</p>
113+
116114
<p>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.</p>
115+
</section>
117116

118-
<p>A summary of this report and others can be found as part of the <a href="https://w3c.github.io/typography/gap-analysis/language-matrix.html" style="font-size: 140%;">language matrix</a>.</p>
119117

120-
<p>For a description of the Gujarati script see the (non-W3C) page <a href="https://r12a.github.io/scripts/gujr/gu.html">Gujarati Orthography Notes</a>, which summarises aspects of the orthography and typographic features, including relevant Unicode characters and their use.</p>
121-
</section>
122118

123119

124120

125121

126122

127-
<section id="workflow">
128-
<h3>Work flow</h3>
129-
<p><span style="font-weight:bold; font-size: 140%;">This version of the document is a preliminary analysis</span></p>
123+
<section id="prioritization">
124+
<h3>Prioritization</h3>
130125

131-
<p>Gap analysis work usually starts with a <strong>preliminary analysis</strong>, conducted quickly by one or a small group of experts. Then a more <strong>detailed analysis</strong> 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 <strong>ongoing maintenance</strong>. 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.</p>
132-
133-
<!--p>As the gap analysis develops, the requirements for features that are problematic should be described in the companion document, <a href="https://w3c.github.io/xxxxlreq/">Xxxx Layout Requirements</a>. Links to the appropriate part of that document should be added to this document as the material is created. Note that the requirements document should not contain any technology-specific information: all of that belongs here.</p-->
134-
</section>
135-
136-
<section id="prioritization">
137-
<h3>Prioritization</h3>
138-
<p>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.</p>
139-
140-
<p>Key:</p>
141-
<ul style="list-style-type: none;">
142-
<li class="ok"></li>
143-
<li class="na"></li>
144-
<li class="advanced"></li>
145-
<li class="basic"></li>
146-
<li class="broken"></li>
147-
<li class="tbd"></li>
148-
</ul>
149-
150-
<p>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.</p>
151-
<p>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.</p>
152-
<p>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.</p>
153-
<p>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.) </p>
154-
</section>
126+
<p>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.</p>
127+
128+
<p>Key:</p>
129+
<ul style="list-style-type: none;">
130+
<li class="ok"></li>
131+
<li class="na"></li>
132+
<li class="advanced"></li>
133+
<li class="basic"></li>
134+
<li class="broken"></li>
135+
<li class="tbd"></li>
136+
</ul>
137+
138+
<p>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.</p>
139+
140+
<p>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.</p>
141+
142+
<p>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.</p>
143+
144+
<p>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.) </p>
155145
</section>
156146

157147

158148

159149

160150

161151

152+
<section id="related">
153+
<h2>Related information</h2>
154+
155+
<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank">Language Matrix</a>.</p>
156+
157+
<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" target="_blank">Gap Analysis Pipeline</a>. (<a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Agujr%22" target="_blank">Filter for Gujarati script items</a>)</p>
158+
159+
<!--<p>See also <a href="https://www.w3.org/TR/gujr-lreq/" target="_blank">Gujarati Script Resources</a> for information about the Gujarati script.</p>-->
160+
</section>
161+
</section>
162+
163+
164+
165+
166+
162167

163168

164169

0 commit comments

Comments
 (0)