8000 First draft lreq docs for Lao, Thai, Khmer & Javanese · w3c/sealreq@bdff54e · GitHub
[go: up one dir, main page]
Skip to content

Commit bdff54e

Browse files
r12ar12a
committed
First draft lreq docs for Lao, Thai, Khmer & Javanese
1 parent 4b0d603 commit bdff54e

File tree

13 files changed

+1242
-110
lines changed

13 files changed

+1242
-110
lines changed

‎javanese/images/line-break-taling.png‎

21.3 KB
Loading

‎javanese/images/pangandika.png‎

22.7 KB
Loading

‎javanese/index.html‎

Lines changed: 236 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,236 @@
1+
<!DOCTYPE html>
2+
3+
<html lang="en">
4+
<head>
5+
<meta charset="utf-8">
6+
7+
<title>Javanese Layout Requirements (Draft)</title>
8+
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" async="" class="remove" type="text/javascript">
9+
</script>
10+
<script class="remove" type="text/javascript">
11+
var respecConfig = {
12+
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
13+
specStatus: "ED",
14+
//publishDate: "2015-07-21",
15+
//previousPublishDate: "2014-12-16",
16+
//previousMaturity: "FPWD",
17+
18+
noRecTrack: true,
19+
shortName: "javanese-lreq",
20+
copyrightStart: "2019",
21+
edDraftURI: "http://w3c.github.io/sealreq/javanese/",
22+
23+
// if this is a LCWD, uncomment and set the end of its review period
24+
// lcEnd: "2009-08-05",
25+
26+
// editors, add as many as you like
27+
// only "name" is required
28+
editors: [
29+
{ name: "Richard Ishida", company: "W3C" }
30+
],
31+
32+
33+
wg: "Internationalization Working Group",
34+
wgURI: "http://www.w3.org/International/core/",
35+
wgPublicList: "public-i18n-sealreq",
36+
bugTracker: { new: "https://github.com/w3c/sealreq/issues", open: "https://github.com/w3c/sealreq/issues" } ,
37+
otherLinks: [
38+
{
39+
key: "Github",
40+
data: [
41+
{
42+
value: "repository",
43+
href: "https://github.com/w3c/sealreq"
44+
}
45+
]
46+
}
47+
],
48+
49+
// URI of the patent status for this WG, for Rec-track documents
50+
// !!!! IMPORTANT !!!!
51+
// This is important for Rec-track documents, do not copy a patent URI from a random
52+
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
53+
// Team Contact.
54+
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/32113/status",
55+
// !!!! IMPORTANT !!!! MAKE THE ABOVE BLINK IN YOUR HEAD
56+
};
57+
</script>
58+
<link rel="stylesheet" href="local.css" type="text/css">
59+
</head>
60+
61+
<body>
62+
<div id="abstract">
63+
<p>This document describes requirements for the layout and presentation of text in languages that use the Javanese script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.</p>
64+
</div>
65+
66+
<div id="sotd">
67+
<p>This document describes the basic requirements for Javanese 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 the Javanese script. Currently the document focuses on Javanese as used for the Javanese language. The information here is developed in conjunction with a <a href="../gap-analysis/javanese-gap.html">document that summarises gaps</a> in support on the Web for Javanese script.</p>
68+
<p>The editor's draft of this document is being developed by the <a href="http://www.w3.org/International/groups/sealreq-layout/">Southeast Asian Layout Task Force</a>, part of the W3C <a href="http://www.w3.org/International/ig/">Internationalization Interest Group</a>. It is published by the <a href="http://www.w3.org/International/core/">Internationalization Working Group</a>. The end target for this document is a Working Group Note.</p>
69+
70+
<div class="note">
71+
<p data-lang="en" style="font-weight: bold; font-size: 120%">Sending comments on this document</p>
72+
73+
<p data-lang="en">If you wish to make comments regarding this document, please raise them as <a href="https://github.com/w3c/sealreq/issues" style="font-size: 120%;">github issues</a> <!--against the <a href="http://www.w3.org/TR/2015/WD-ilreq-20150721/" style="font-size: 120%">latest dated version in /TR</a>-->. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.</p>
74+
75+
<p data-lang="en">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&nbsp; using a URL.</p>
76+
</div>
77+
</div>
78+
79+
<section id="h_introduction">
80+
<h2>Introduction</h2>
81+
82+
<section id="h_about_this_document">
83+
<h3>About this document</h3>
84+
85+
<p>Some text goes here.</p>
86+
</section>
87+
88+
<section id="h_gap_analysis">
89+
<h3>Gap analysis</h3>
90+
91+
<p>This document is pointed to by a separate document, <a href="../gap-analysis/javanese-gap.html">Javanese Gap Analysis</a>, which describes gaps in support for Javanese on the Web, and prioritises and describes the impact of those gaps on the user.</p>
92+
<p>Wherever an unsupported feature is indentified through the gap analysis process, the requirements for that feature need to be documented. This document is where those requirements are described.</p>
93+
<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>
94+
</section>
95+
96+
97+
<section id="h_info_requests">
98+
<h3>Other related resources</h3>
99+
100+
<p>The document <a href="https://w3c.github.io/typography/">International text layout and typography index</a> (known informally as the text layout index) points to this document and others, and provides a central location for developers and implementers to find information related to various scripts.</p>
101+
<p>The W3C also maintains a tracking system that has links to github issues in W3C repositories. There are separate links for (a) requests from developers to the user community for information about how scripts/languages work, (b) issues raised against a spec, and (c) browser bugs. For example, you can find out <a href="http://w3c.github.io/i18n-activity/textlayout/?filter=type-info-request">what information developers are currently seeking</a>, and the resulting list can also be filtered by script.</p>
102+
</section>
103+
104+
105+
</section>
106+
<section id="h_script_overview">
107+
<h2>Javanese Script Overview</h2>
108+
<p> Javanese is an <span class="newterm"><a class="termref" href="https://www.unicode.org/glossary/#abugida">abugida</a></span>, ie. consonants carry an inherent vowel sound that is overridden, where needed, using vowel signs. In Javanese, consonants carry an inherent vowel, which can be <span class="trans">a</span> or <span class="trans">o</span>.</p>
109+
<p>An orthographic syllable in Javanese can be described as {C F} C {{R}Y} {V{A}} {Z}, where: </p>
110+
<ul>
111+
<li>C is a consonant (or consonant + <span class="codepoint"><span lang="jv">◌꦳</span> [<span class="uname">U+A9B3 JAVANESE SIGN CECAK TELU​</span>]</span>), </li>
112+
<li>F is <span class="codepoint"><span lang="jv">◌꧀</span> [<span class="uname">U+A9C0 JAVANESE PANGKON​</span>]</span>, </li>
113+
<li>R is<span class="codepoint"><span lang="jv">◌ꦿ</span> [<span class="uname">U+A9BF JAVANESE CONSONANT SIGN CAKRA​</span>]</span>, </li>
114+
<li>Y is <span class="codepoint"><span lang="jv">◌ꦾ</span> [<span class="uname">U+A9BE JAVANESE CONSONANT SIGN PENGKAL​</span>]</span>, </li>
115+
<li>V is a vowel-sign, </li>
116+
<li>A is <span class="codepoint"><span lang="jv">◌ꦴ</span> [<span class="uname">U+A9B4 JAVANESE VOWEL SIGN TARUNG​</span>]</span>, and </li>
117+
<li>Z is one of the syllable-final consonants.</li>
118+
</ul>
119+
<p>The initial consonant cluster may represent a word-initial cluster such as <span class="trans">mb</span>, <span class="trans">nd</span>, <span class="trans">ndh</span>, <span class="trans">nj</span> or <span class="trans">nng</span>,<sup><a href="#refs">c</a></sup> eg. <span class="charExample" translate="no"><span class="ex" lang="jv">ꦩꦧꦸꦫꦸ</span> <span class="trans">mburu</span> <span class="meaning">hunting</span></span>, or it may represent the final consonant of a preceding syllable and the initial consonant of another, eg. <span class="charExample" translate="no"><span class="ex" lang="jv">ꦲꦏ꧀ꦱꦫ</span> <span class="trans">hk͓sr (aksara)</span> <span class="meaning">characters</span></span>.</p>
120+
<p>Root words are typically disyllables of the form Cˡ V Cˡ V Cˡ, where Cˡ represents an optional consonant or consonant cluster, and V represents a vowel. Most commonly, this represents CVCVC, followed by CVCCVC.<sup><a href="#refs">c</a></sup></p>
121+
</section>
122+
123+
124+
125+
126+
127+
<section>
128+
<h2 id="h_text_direction">Text direction</h2>
129+
130+
<p>Javanese is written horizontally, left to right.</p>
131+
132+
</section>
133+
134+
135+
136+
137+
138+
<section id="h_characters_and_phrases">
139+
<h2>Structural boundaries &amp; markers</h2>
140+
141+
142+
<section id="h_words">
143+
<h3>Word boundaries</h3>
144+
<p>The concept of 'word' is difficult to define in any language (see <a href="https://www.w3.org/International/articles/typography/linebreak.en#whatisword">What is a word?</a>). We will treat it as a vaguely-defined but recognisable semantic unit that is typically smaller than a phrase and may comprise one or more syllables.</p>
145+
<p>Spaces are used in Javanese as phrase separators, but Javanese doesn't separate words in a phrase using visible spaces. </p>
146+
</section>
147+
<section id="h_quotations">
148+
<h3>Quotations</h3>
149+
<p>Javanese text may use <span class="codepoint"><span lang="jv">꧊</span> [<span class="uname">U+A9CA JAVANESE PADA ADEG</span>]</span> for quotation marks.<span class="charExample"><span class="ex" lang="hy"></span></span></p>
150+
<p><span class="codepoint">Alternatively, the pair of characters <span lang="jv">꧌</span> [<span class="uname">U+A9CC JAVANESE PADA PISELEH</span>] and <span lang="jv">꧍</span> [<span class="uname">U+A9CD JAVANESE TURNED PADA PISELEH</span>] may be used.</span></p>
151+
</section>
152+
153+
154+
<section id="h_segmentation">
155+
<h3>Text boundaries &amp; selection</h3>
156+
<p class="prompt">TBD</p>
157+
</section>
158+
</section>
159+
160+
161+
162+
163+
164+
165+
<section id="h_lines_and_paragraphs">
166+
<h2>Line &amp; paragraph layout</h2>
167+
168+
<section id="h_line_breaking">
169+
<h3>Line breaking</h3>
170+
171+
<p>Like Tibetan, line breaking can occur after any full orthographic syllable. Hyphenation is not used.<sup><a href="https://github.com/w3c/sealreq/issues/2#issuecomment-388524506">→g</a></sup></p>
172+
<p>Javanese stacks consonants when they occur without intervening vowels, and this stacking occurs across word and syllable boundaries. When breaking a line, these stacks are not split. Similarly, some consonant clusters are rendered with conjoined glyphs, which should also not be broken. This means that line-breaking is done at the boundaries of 'orthographic syllables', rather than phonetic ones.</p>
173+
<p>The example in the figure below shows the Javanese words <span class="trans">pangan</span> and <span class="trans">dika</span>. The final <span class="trans">n</span> in <span class="trans">pangan</span> and the initial <span class="trans">di</span> in <span class="trans">dika</span> form a stack. The line break opportunity appears just before the stack, which means that the final <span class="trans">n</span> in <span class="trans">pangan</span> will be wrapped to the next line with the word <span class="trans">dika</span>.</p>
174+
<figure>
175+
<p><img src="images/pangandika.png" alt=""></p>
176+
<figcaption>Line break opportunity between the words pangan and dika (red line) splits the final consonant from pangan<span class="trans"></span>.</figcaption>
177+
</figure>
178+
179+
<p>In some printed material, when a new line begins with <span class="codepoint"><span lang="jv">ꦺ</span> [<span class="uname">U+A9BA JAVANESE VOWEL SIGN TALING</span>]</span>, an additional spacing glyph of the same character is placed at the end of the previous line.</p>
180+
<figure>
181+
<p><img src="images/line-break-taling.png" alt=""></p>
182+
<figcaption>An extra taling at the end of the line when the word <span class="trans">kawon</span> is split before <span class="trans">won</span>.</figcaption>
183+
</figure>
184+
</section>
185+
186+
187+
188+
189+
<section id="h_alignment"> </section>
190+
</section>
191+
192+
193+
194+
195+
196+
197+
198+
<!--section class="appendix" id="glossary">
199+
<h2>Glossary</h2>
200+
201+
<table class="glossary">
202+
<thead>
203+
<tr>
204+
<th>Term</th>
205+
206+
<th>XXXX</th>
207+
208+
<th>Transliteration</th>
209+
210+
<th>Definition</th>
211+
</tr>
212+
</thead>
213+
214+
<tbody>
215+
<tr id="def_alignment">
216+
<td>alignment</td>
217+
218+
<td class="rtlTermCell">&nbsp;</td>
219+
220+
<td class="rtlTermCell">&nbsp;</td>
221+
222+
<td><br></td>
223+
</tr>
224+
</tbody>
225+
</table>
226+
</section-->
227+
228+
<section class="appendix" id="acknowledgements">
229+
<h2>Acknowledgements</h2>
230+
231+
<p>Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).</p>
232+
<p>Ben Mitchell, Danh Hong, Marc Durdin, Martin Hosken.</p>
233+
<p data-lang="en">Please find the latest info of the contributors at the <a href="https://github.com/w3c/sealreq/graphs/contributors">GitHub contributors list</a>.</p>
234+
</section>
235+
</body>
236+
</html>

‎javanese/local.css‎

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
2+
3+
h2 {
4+
margin-top: 4em !important;
5+
margin-bottom: 0em !important;
6+
}
7+
.head h2, #abstract h2, #sotd h2 {
8+
margin-top: 0 !important;
9+
}
10+
h3 {
11+
margin-top: 3em !important;
12+
}
13+
h4 {
14+
font-size: 100%;
15+
font-weight: normal;
16+
color: #005a9c;
17+
margin-top: 2em;
18+
}
19+
.leadin {
20+
font-weight: bold;
21+
}
22+
23+
ins {
24+
background-color: #99FF99;
25+
text-decoration: none;
26+
}
27+
del {
28+
display: inline;
29+
color: silver;
30+
}
31+
32+
figure {
33+
margin-bottom: 2em;
34+
text-align: center;
35+
}
36+
figcaption {
37+
text-align: center;
38+
margin: 0.5em 2em;
39+
font-style: italic;
40+
font-size: 90%;
41+
}
42+
.figno:after {
43+
content: ':\00A0 ';
44+
}
45+
46+
a.termref:link {
47+
color:#C60;
48+
text-decoration:none;
49+
border-bottom: 1px dotted #FC0;
50+
}
51+
a.termref:hover {
52+
color:#C60;
53+
text-decoration:none;
54+
border-bottom: 1px dotted #FC0;
55+
}
56+
a.termref:visited {
57+
color:#C60;
58+
text-decoration:none;
59+
border-bottom: 1px dotted #FC0;
60+
}
61+
a.termref:active {
62+
color:#C60;
63+
text-decoration:none;
64+
border-bottom: 1px dotted #FC0;
65+
}
66+
67+
.qterm:before, .qchar:before { content: "'"; }
68+
.qterm:after, .qchar:after { content: "'"; }
69+
.quote:before { content: '"'; }
70+
.quote:after { content: '"'; }
71+
code {
72+
color: #A52A2A;
73+
font-family: Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", monospace;
74+
font-size: 100%;
75+
}
76+
samp, kbd {
77+
font-family: Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", monospace;
78+
font-size: 100%;
79+
}
80+
.uname {
81+
text-transform: uppercase;
82+
font-size: 85%;
83+
letter-spacing:0.03em;
84+
}
85+
.prompt {
86+
font-style: italic;
87+
color: #aaa;
88+
font-size: 90%;
89+
margin-bottom: 4em;
90+
}
91+
92+
.large {
93+
font-size: 300%;
94+
}
95+
.trans, .ipa {
96+
font-family: "GentiumPlus", serif;
97+
font-style: italic;
98+
}
99+
.meaning:before {
100+
content:"‘";
101+
}
102+
.meaning:after {
103+
content:"’";
104+
}

‎khmer/images/font_style_chor.png‎

2.48 KB
Loading

‎khmer/images/font_style_chrieng.png‎

3.06 KB
Loading

‎khmer/images/font_style_mul.png‎

3.64 KB
Loading

0 commit comments

Comments
 (0)
0