Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit ff37042

Browse filesBrowse files
committed
guru Remove duplicate front matter. + echidna file
1 parent 21ec733 commit ff37042
Copy full SHA for ff37042

File tree

2 files changed

+4
-100
lines changed
Filter options

2 files changed

+4
-100
lines changed

‎guru/echidna

Copy file name to clipboard
+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# ECHIDNA configuration
2+
index.html?specStatus=DNOTE&shortName=guru-lreq respec

‎guru/index.html

Copy file name to clipboardExpand all lines: guru/index.html
+2-100
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
var respecConfig = {
1111
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
1212
specStatus: "ED",
13-
//publishDate: "2020-06-16",
13+
//publishDate: "2024-07-23",
1414

1515
noRecTrack: true,
1616
shortName: "guru-lreq",
@@ -43,7 +43,7 @@
4343
</script>
4444

4545
<link rel="stylesheet" data-import href="https://w3c.github.io/i18n-drafts/style/respec_2022.css">
46-
<link rel="stylesheet" href="local.css">
46+
<!--<link rel="stylesheet" href="local.css">-->
4747
</head>
4848

4949
<body>
@@ -151,104 +151,6 @@ <h3>Related resources</h3>
151151

152152

153153

154-
<div id="abstract">
155-
<p>This document describes or points to requirements for the layout and presentation of text in languages that use the Gurmukhi script. The target audience is developers of Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode, as well as implementers of web browsers, ebook readers, and other applications that need to render Gurmukhi text.</p>
156-
</div>
157-
158-
<div id="sotd">
159-
<p>This document describes the basic requirements for Gurmukhi script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications about how to support users of Gurmukhi script languages. Currently the document focuses on the Gurmukhi script as used for Gurmukhi. The information here is developed in conjunction with a <a href="https://www.w3.org/TR/guru-gap/">document that summarises gaps</a> in support on the Web for Gurmukhi.</p>
160-
161-
<p>The editor's draft of this document is being developed by the <a href="https://w3c.github.io/mlreq/">India Layout Task Force</a>, part of the W3C <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>
162-
163-
<p>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.</p>
164-
</div>
165-
166-
167-
<div id="linkWarning">
168-
<p>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.</p>
169-
170-
<p>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.</p>
171-
</div>
172-
173-
174-
175-
176-
177-
178-
179-
180-
181-
182-
183-
<section id="h_introduction">
184-
<h2>Introduction</h2>
185-
186-
187-
188-
<section id="h_acknowledgements">
189-
<h3>Contributors</h3>
190-
191-
<p>The initial version of this document was prepared by Richard Ishida.</p>
192-
193-
<!--<p>Thanks to the following people who contributed information that is used in this document (contributors' names listed in in alphabetic order): XXXX.</p>
194-
-->
195-
<p data-lang="en">See also the <a href="https://github.com/w3c/iip/graphs/contributors">GitHub contributors list</a> for the Gurmukhi Language Enablement project, and the <a href="https://github.com/w3c/iip/issues?q=is%3Aopen+is%3Aissue">discussions related to Gurmukhi script</a>.</p>
196-
</section>
197-
198-
199-
200-
201-
202-
203-
<section id="h_about_this_document">
204-
<h3>About this document</h3>
205-
206-
<p>The aim of this document is to describe the basic requirements for Gurmukhi script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of the Gurmukhi script. The document currently focuses on texts using the Gurmukhi language.</p>
207-
208-
<p>The document focuses on typographic layout issues. For a deeper understanding of Gurmukhi using the Gurmukhi script and how it works see <cite>Panjabi (Gurmukhi) Orthography Notes</cite>, which includes topics such as: <a href="https://r12a.github.io/scripts/guru/pa.html#phonology">Phonology</a>, <a href="https://r12a.github.io/scripts/guru/pa.html#vowels">Vowels</a>, <a href="https://r12a.github.io/scripts/guru/pa.html#consonants">Consonants</a>, <a href="https://r12a.github.io/scripts/guru/pa.html#encoding">Encoding choices</a>, and <a href="https://r12a.github.io/scripts/guru/pa.html#numbers">Numbers</a>.</p>
209-
210-
<p>This document should contain no reference to a particular technology. For example, it should not say &quot;CSS does/doesn't do such and such&quot;, 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.</p>
211-
</section>
212-
213-
214-
215-
216-
217-
218-
<section id="h_gap_analysis">
219-
<h3>Gap analysis</h3>
220-
221-
<p>This document should be used alongside a separate document, <a href="https://www.w3.org/TR/guru-gap/"><cite>Gurmukhi Gap Analysis</cite></a>, which describes gaps in support for Gurmukhi on the Web, and prioritises and describes the impact of those gaps on the user.</p>
222-
223-
<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%22doc%3Aarab_ks%22" target="_blank">Filter it for Kashmiri</a>)</p>
224-
</section>
225-
226-
227-
228-
229-
230-
231-
232-
<section id="h_info_requests">
233-
<h3>Other related resources</h3>
234-
235-
<p>To complement any content authored specifically for this document, the sections in the document also point to related, external information, tests, GitHub discussions, etc.</p>
236-
237-
<p>The document <a href="https://www.w3.org/TR/typography/"><cite>Language enablement index</cite></a> points to this document and others, and provides a central location for developers and implementers to find information related to various scripts.</p>
238-
239-
<p>The <abbr title="World Wide Web Consortium">W3C</abbr> also has a repository with discussion threads related to the Gurmukhi script, including requests from developers to the user community for information about how scripts/languages work, and a notification system that tracks issues in <abbr title="World Wide Web Consortium">W3C</abbr> working groups related to the Gurmukhi script. See a list of <a target="_blank" href="https://github.com/w3c/iip/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion+">unresolved questions</a> for Gurmukhi experts. Each section below points to related discussions. See also the <a href="https://w3c.github.io/iip/home">repository home page</a>.</p>
240-
</section>
241-
</section>
242-
243-
244-
245-
246-
247-
248-
249-
250-
251-
252154

253155

254156

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.