Skip to content

Commit 5018b8e

Browse files
committed
lreq docs Fix heading ids to match labels. Add echidna.
1 parent c5caf32 commit 5018b8e

File tree

6 files changed

+100
-94
lines changed

6 files changed

+100
-94
lines changed

‎cans/echidna

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# ECHIDNA configuration
2+
index.html?specStatus=DNOTE&shortName=cans-lreq respec

‎cans/index.html

Lines changed: 31 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -251,10 +251,10 @@ <h2>All topics</h2>
251251

252252

253253
<section>
254-
<h2 id="h_text_direction">Text direction</h2>
254+
<h2 id="direction">Text direction</h2>
255255

256256

257-
<section id="h_vertical_text">
257+
<section id="vertical_text">
258258
<h3>Vertical text</h3>
259259

260260
<aside class="prompts">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?</aside>
@@ -323,7 +323,7 @@ <h3>Vertical text</h3>
323323

324324

325325
<!--
326-
<section id="h_bidi_text">
326+
<section id="bidi_text">
327327
<h3>Bidirectional text</h3>
328328
329329
<aside class="prompts">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?</aside>
@@ -403,7 +403,7 @@ <h3>Bidirectional text</h3>
403403
<h2>Glyph shaping &amp; positioning</h2>
404404

405405

406-
<section id="h_writing_styles">
406+
<section id="fonts">
407407
<h3>Fonts &amp; font styles</h3>
408408

409409
<aside class="prompts">How are fonts grouped into recognisable writing styles? How is each writing style used? Are OpenType features needed? What other font-related requirements and issue exist?</aside>
@@ -487,7 +487,7 @@ <h3>Fonts &amp; font styles</h3>
487487

488488

489489

490-
<section class="h_context">
490+
<section id="glyphs">
491491
<h3>Context-based shaping &amp; positioning</h3>
492492

493493
<aside class="prompts">Are special glyph forms needed, depending on the context in which a character is used? Do glyphs interact in some circumstances? Are there requirements to position diacritics or other items specially, depending on context? Does the script have multiple diacritics competing for the same location relative to the base?</aside>
@@ -560,7 +560,7 @@ <h3>Context-based shaping &amp; positioning</h3>
560560

561561

562562
<!--
563-
<section class="h_cursive">
563+
<section id="cursive">
564564
<h3>Cursive text</h3>
565565
566566
<aside class="prompts">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?</aside>
@@ -630,7 +630,7 @@ <h3>Cursive text</h3>
630630

631631

632632

633-
<section class="h_fontstyle">
633+
<section id="letterforms">
634634
<h3>Letterform slopes, weights, &amp; italics</h3>
635635

636636
<aside class="prompts">Are italicisation, bolding, oblique, etc relevant? 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?</aside>
@@ -701,7 +701,7 @@ <h3>Letterform slopes, weights, &amp; italics</h3>
701701

702702

703703

704-
<!--<section class="h_transforms">
704+
<!--<section id="transforms">
705705
<h3>Case &amp; other character transforms</h3>
706706
707707
<aside class="prompts">Is the orthography bicameral? Are there other character pairings, especially when transforms are needed to convert between the two?</aside>
@@ -772,13 +772,13 @@ <h3>Case &amp; other character transforms</h3>
772772

773773

774774

775-
<section class="h_graphemes">
775+
<section class="h_segmentation">
776776
<h2>Typographic units</h2>
777777

778778

779779

780780

781-
<section class="h_transforms">
781+
<section id="encoding">
782782
<h3>Characters &amp; encoding</h3>
783783

784784

@@ -856,7 +856,7 @@ <h3>Characters &amp; encoding</h3>
856856

857857

858858

859-
<section class="h_segmentation">
859+
<section id="segmentation">
860860
<h3>Grapheme/word segmentation &amp; selection</h3>
861861

862862
<aside class="prompts">Do Unicode grapheme clusters appropriately segment character units for the script? Are there special requirements for the following operations: forwards/backwards deletion, cursor movement &amp; selection, character counts, searching &amp; matching, text insertion, line-breaking, justification, case conversions, sorting? Are words separated by spaces, or other characters? Are there special requirements when double-clicking on the text? Are words hyphenated?</aside>
@@ -941,12 +941,12 @@ <h3>Grapheme/word segmentation &amp; selection</h3>
941941

942942

943943

944-
<section id="h_characters_and_phrases">
944+
<section id="h_inline">
945945
<h2>Punctuation &amp; inline features</h2>
946946

947947

948948

949-
<section id="h_phrase">
949+
<section id="punctuation_etc">
950950
<h3>Phrase &amp; section boundaries</h3>
951951

952952

@@ -1020,7 +1020,7 @@ <h3>Phrase &amp; section boundaries</h3>
10201020

10211021

10221022

1023-
<section id="h_quotations">
1023+
<section id="quotations">
10241024
<h3>Quotations &amp; citations</h3>
10251025

10261026

@@ -1091,7 +1091,7 @@ <h3>Quotations &amp; citations</h3>
10911091

10921092

10931093

1094-
<section id="h_emphasis">
1094+
<section id="emphasis">
10951095
<h3>Emphasis &amp; highlighting</h3>
10961096

10971097

@@ -1161,7 +1161,7 @@ <h3>Emphasis &amp; highlighting</h3>
11611161

11621162

11631163

1164-
<section id="h_abbrev">
1164+
<section id="abbrev">
11651165
<h3>Abbreviation, ellipsis &amp; repetition</h3>
11661166

11671167

@@ -1231,7 +1231,7 @@ <h3>Abbreviation, ellipsis &amp; repetition</h3>
12311231

12321232

12331233

1234-
<section id="h_inlinenotes">
1234+
<section id="inline_notes">
12351235
<h3>Inline notes &amp; annotations</h3>
12361236

12371237

@@ -1301,7 +1301,7 @@ <h3>Inline notes &amp; annotations</h3>
13011301

13021302

13031303

1304-
<section id="h_otherinline">
1304+
<section id="text_decoration">
13051305
<h3>Text decoration &amp; other inline features</h3>
13061306

13071307

@@ -1374,7 +1374,7 @@ <h3>Text decoration &amp; other inline features</h3>
13741374

13751375

13761376

1377-
<section id="h_data_formats">
1377+
<section id="data_formats">
13781378
<h3>Data formats &amp; numbers</h3>
13791379

13801380

@@ -1451,11 +1451,11 @@ <h3>Data formats &amp; numbers</h3>
14511451

14521452

14531453

1454-
<section id="h_lines_and_paragraphs">
1454+
<section id="h_para">
14551455
<h2>Line &amp; paragraph layout</h2>
14561456

14571457

1458-
<section id="h_line_breaking">
1458+
<section id="line_breaking">
14591459
<h3>Line breaking &amp; hyphenation</h3>
14601460

14611461
<aside class="prompts">Are there special rules about the way text 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? Is hyphenation used, or something else? What rules are used? What difficulties exist?</aside>
@@ -1524,7 +1524,7 @@ <h3>Line breaking &amp; hyphenation</h3>
15241524

15251525

15261526

1527-
<section id="h_alignment">
1527+
<section id="justification">
15281528
<h3>Text alignment &amp; justification</h3>
15291529

15301530
<aside class="prompts">Does text in a paragraph needs to have flush lines down both sides? Does the 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? Does the script shrink/stretch space between words and/or letters? Are word baselines stretched, as in Arabic? What about paragraph indents?</aside>
@@ -1591,7 +1591,7 @@ <h3>Text alignment &amp; justification</h3>
15911591

15921592

15931593

1594-
<section id="h_spacing">
1594+
<section id="spacing">
15951595
<h3>Text spacing</h3>
15961596

15971597
<aside class="prompts">This section looks at ways in which spacing is applied between characters over and above that which is introduced during justification. For example, does the orthography create emphasis or other effects by spacing out the words, letters or syllables in a word? (For justification related spacing, see Text alignment &amp; justification, above).</aside>
@@ -1655,7 +1655,7 @@ <h3>Text spacing</h3>
16551655

16561656

16571657

1658-
<section id="h_baselines">
1658+
<section id="baselines">
16591659
<h3>Baselines, line height, etc.</h3>
16601660

16611661
<aside class="prompts">Does the script have special requirements for baseline alignment between mixed scripts and in general? Is line height special for this script? Are there other aspects that affect line spacing, or positioning of items vertically within a line?</aside>
@@ -1721,7 +1721,7 @@ <h3>Baselines, line height, etc.</h3>
17211721

17221722

17231723

1724-
<section id="h_counters">
1724+
<section id="lists">
17251725
<h3>Lists, counters, etc.</h3>
17261726

17271727
<aside class="prompts">Are there list or other counter styles in use? If so, what is the format used? Do counters need to be upright in vertical text? Are there other aspects related to counters and lists that need to be addressed?</aside>
@@ -1798,7 +1798,7 @@ <h3>Lists, counters, etc.</h3>
17981798

17991799

18001800

1801-
<section id="h_initials">
1801+
<section id="initials">
18021802
<h3>Styling initials</h3>
18031803

18041804
<aside class="prompts">Does the script use 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? Are dropped, sunken, and raised types found? etc.</aside>
@@ -1879,7 +1879,7 @@ <h2>Page &amp; book layout</h2>
18791879

18801880
<p>tbd</p>
18811881

1882-
<!--<section id="h_generallayout">
1882+
<!--<section id="page_layout">
18831883
<h3>General page layout &amp; progression</h3>
18841884
18851885
<aside class="prompts">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. When content can flow vertically and to the left or right, how to specify the location of objects, text, etc. relative to the flow? Do tables and grid layouts work as expected? How do coluLANGTAGs work in vertical text? Can you mix block of vertical and horizontal text? Does text scroll in a different direction?</aside>
@@ -1945,7 +1945,7 @@ <h3>General page layout &amp; progression</h3>
19451945
19461946
19471947
1948-
<section id="h_grids_tables">
1948+
<section id="grids_tables">
19491949
<h3>Grids &amp; tables</h3>
19501950
19511951
<aside class="prompts">Does the script have special requirements for character grids or tables?</aside>
@@ -2011,7 +2011,7 @@ <h3>Grids &amp; tables</h3>
20112011
20122012
20132013
2014-
<section id="h_footnotes_etc">
2014+
<section id="footnotes_etc">
20152015
<h3>Footnotes, endnotes, etc</h3>
20162016
20172017
<aside class="prompts">Support for footnotes, endnotes or other necessary annotations of this kind may vary in other cultures. In some cases, a script may use a very idiosyncratic approach to locate the notes or to link to them from the text. (See Inline notes &amp; annotations for purely inline annotations, such as ruby or warichu. This section is about annotation systems that separate the reference marks and the content of the notes.)</aside>
@@ -2080,7 +2080,7 @@ <h3>Footnotes, endnotes, etc</h3>
20802080
20812081
20822082
2083-
<section id="h_headers_footers">
2083+
<section id="headers_footers">
20842084
<h3>Page headers, footers, etc</h3>
20852085
20862086
<aside class="prompts">Are there special conventions for page numbering, or the way that running headers and the like are handled?</aside>
@@ -2149,7 +2149,7 @@ <h3>Page headers, footers, etc</h3>
21492149
21502150
21512151
2152-
<section id="h_interaction">
2152+
<section id="interaction">
21532153
<h3>Forms &amp; user interaction</h3>
21542154
21552155
<aside class="prompts">Are vertical form controls needed? Are scroll bars in an unusual position? Other special requirements for user interaction?</aside>

‎cher/echidna

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# ECHIDNA configuration
2+
index.html?specStatus=DNOTE&shortName=cher-lreq respec

0 commit comments

Comments
 (0)