Skip to content

Commit 599d848

Browse files
anushahhanushahh
authored
Set up redirect
1 parent 37b1cb1 commit 599d848

1 file changed

Lines changed: 6 additions & 198 deletions

File tree

‎proposal-questions.html‎

Lines changed: 6 additions & 198 deletions
Original file line numberDiff line numberDiff line change
@@ -1,201 +1,9 @@
1-
<!DOCTYPE html>
2-
<html lang="en">
1+
<!doctype html>
2+
<html>
33
<head>
4-
<meta charset="UTF-8">
5-
<meta name="viewport" content="width=device-width, initial-scale=1.0">
6-
<title>Proposal Questions | Script Encoding Initiative</title>
7-
<meta name="description" content="Encoding scripts in Unicode since 2002.">
8-
9-
<link rel="shortcut icon" href="static/img/favicon.ico" type="image/x-icon">
10-
<link rel="stylesheet" href="static/css/main.css" media="all">
11-
4+
<meta http-equiv="refresh" content="0; url=https://sei.berkeley.edu/tips-for-proposals/" />
5+
<link rel="canonical" href="https://sei.berkeley.edu/tips-for-proposals/" />
6+
<script>window.location.replace("https://sei.berkeley.edu/tips-for-proposals/");</script>
127
</head>
13-
<body>
14-
<nav class="navbar">
15-
<div class="navbar__inner">
16-
<a class="navbar__logo" href="/">Script Encoding Initiative</a>
17-
18-
<div class="navbar__mobile-options">
19-
<div class="navbar__button dark-toggle" aria-label="toggle dark theme">
20-
<img src="static/img/moon.svg" alt="">
21-
</div>
22-
<button class="navbar__button navbar__hamburger" aria-expanded="false" aria-label="toggle menu">
23-
<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 0 24 24" width="24px" fill="#333333">
24-
<path d="M0 0h24v24H0z" fill="none"/>
25-
<path d="M3 18h18v-2H3v2zm0-5h18v-2H3v2zm0-7v2h18V6H3z"/>
26-
</svg>
27-
</button>
28-
</div>
29-
30-
<div class="navbar__links">
31-
32-
<a class="navbar__link " href="scripts-to-encode.html">
33-
Scripts to encode
34-
</a>
35-
<a class="navbar__link " href="progress.html">
36-
Progress
37-
</a>
38-
<a class="navbar__link " href="utc-reports.html">
39-
UTC Reports
40-
</a>
41-
<a class="navbar__link " href="news.html">
42-
News
43-
</a>
44-
<a class="navbar__link " href="press.html">
45-
Press
46-
</a>
47-
<a class="navbar__link " href="about-us.html">
48-
About us
49-
</a>
50-
<a class="navbar__link " href="how-to-donate.html">
51-
Donate
52-
</a>
53-
54-
<div class="navbar__button dark-toggle" aria-label="toggle dark theme">
55-
<img src="static/img/moon.svg" alt="">
56-
</div>
57-
58-
</div>
59-
</div>
60-
61-
<div class="navbar__mobile-links">
62-
63-
</div>
64-
65-
</nav>
66-
67-
68-
<div class="container-sm">
69-
<h1>Proposal Questions</h1>
70-
71-
<p>Type of information needed when reviewing script proposals and general background on Unicode and Unicode proposals.</p>
72-
<p>The script proposals aim to cover the characters used in a given script. A &quot;character&quot; is an abstraction (i.e., Latin lowercase letter &quot;a&quot;), which has various surface forms, or &quot;glyphs&quot; (i.e., the cursive &quot;a&quot; differs from that found in Times New Roman, but both are understood as &quot;a&quot; and are contrasted with a &quot;b&quot;). Unicode encodes just characters but information on glyphs is important to note in the documentation, particularly as a single character can have various contextual glyphs. All of these detailed issues are discussed on the <a href="http://www.unicode.org/">Unicode web site</a> and in the <a href="http://www.unicode.org/book/aboutbook.html">Unicode Standard</a> itself.</p>
73-
<p>The Unicode web site hosts a number of examples of proposals that have been recently accepted. These can help give reviewers a flavor of what is considered a complete proposal. If you wish to view such examples to help in your review, please send us a request and we can point you to one or more good examples.</p>
74-
<ul>
75-
<li>
76-
<p>Are all the characters covered? Are there any missing?</p>
77-
<ul>
78-
<li>
79-
<p>NOTE 1: The charts should cover all the letters/syllabic signs, numbers, and punctuation marks that are not already covered by Unicode. If you are unsure whether a particular letter is already in Unicode, note the name, discuss its use, and provide an image, if possible.</p>
80-
</li>
81-
<li>
82-
<p>NOTE 2: Information on the variants of character should be noted.</p>
83-
</li>
84-
<li>
85-
<p>NOTE 3: Ligatures and precomposed characters (character + combining diacritic) will not be included in Unicode, but such information is useful so that fonts can be created. This information too can be included in the documentation.</p>
86-
</li>
87-
</ul>
88-
</li>
89-
<li>
90-
<p>Information on contextual forms is needed for each character, if applicable (i.e., a Xerox or preferably a scanned image showing how the glyph appears in various positions). Which characters have different shapes depending upon position (initial / medial / final)?</p>
91-
</li>
92-
<li>
93-
<p>Information on the joining classes of the letters is also needed, if applicable (i.e., which letters connect to their neighbors and in what manner, with Xeroxes or scanned images).</p>
94-
</li>
95-
<li>
96-
<p>Information on line-breaking properties is also necessary: can a line-break occur before or after the letter? For example, in English the dollar sign is not to be separated from the following number by a line-break. In the combination &quot;$10&quot;, a &quot;$&quot; cannot appear at the line-end, with &quot;10&quot; on the next.</p>
97-
</li>
98-
<li>
99-
<p>Are the visual representations (&quot;glyphs&quot;) on the chart representative?</p>
100-
</li>
101-
<li>
102-
<p>Are the names of the characters satisfactory?</p>
103-
</li>
104-
<li>
105-
<p>Does the script use any special symbols as numerals? If yes, list all necessary characters. Are any of the alphabetic characters used as numerals? How? Any additional supporting marks needed?</p>
106-
</li>
107-
<li>
108-
<p>Are there any special symbols analogous to ampersand, percent?</p>
109-
</li>
110-
<li>
111-
<p>Are there special symbols for literary use: verse sign, page mark, end of paragraph, end of text, etc. Are there any religious symbols?</p>
112-
</li>
113-
<li>
114-
<p>Are all the necessary combining marks listed?</p>
115-
<ul>
116-
<li>NOTE: Some may already be covered elsewhere in Unicode, but I can help check this.</li>
117-
</ul>
118-
</li>
119-
<li>
120-
<p>Languages: Please list any other requirements of languages that use the script.</p>
121-
</li>
122-
<li>
123-
<p>Which characters have glyphs that fall below the baseline?</p>
124-
</li>
125-
<li>
126-
<p>What ligatures are needed? (This information is helpful for font developers.)</p>
127-
</li>
128-
</ul>
129-
130-
131-
<br><hr>
132-
<a href=".">&larr; Back home</a>
133-
</div>
134-
135-
<footer class="footer">
136-
137-
<div class="footertop"
138-
<p><a href="how-to-donate.html">Join</a> our <a href="donors.html">donors</a> today and help to promote native-language education, universal literacy and cultural preservation. Many thanks to:</p>
139-
<br / >
140-
</div>
141-
<div class="logos">
142-
<img class="logo" src="static/img/neh_logo.png"/>
143-
<img class="logo" src="static/img/adobe.svg" />
144-
<img class="logo" src="static/img/unesco.svg" />
145-
<img class="logo" src="static/img/wikimedia_foundation.svg" />
146-
<img class="logo" src="static/img/google_2015.svg" />
147-
<img class="logo" src="static/img/luce.jpeg" />
148-
<img class="logo" src="static/img/monotype.jpeg" />
149-
</div>
150-
</footer>
151-
152-
<script>
153-
const ham = document.querySelector('.navbar__hamburger')
154-
const menu = document.querySelector('.navbar__mobile-links')
155-
const darkToggleButtons = document.querySelectorAll('.dark-toggle')
156-
157-
function changeDarkToggleBtnIcon () {
158-
darkToggleButtons.forEach(btn => {
159-
if (btn.querySelector('img').src.indexOf('static/img/moon.svg') !== -1) {
160-
btn.querySelector('img').src = "static/img/sun.svg"
161-
} else {
162-
btn.querySelector('img').src = "static/img/moon.svg"
163-
}
164-
})
165-
}
166-
167-
if (
168-
localStorage.prefsDark === 'true' ||
169-
(
170-
window.matchMedia &&
171-
window.matchMedia('(prefers-color-scheme: dark)').matches &&
172-
localStorage.prefsDark !== 'false')
173-
) {
174-
document.body.classList.add('dark')
175-
changeDarkToggleBtnIcon()
176-
}
177-
178-
ham.addEventListener('click', () => {
179-
menu.classList.toggle('navbar__mobile-links--open')
180-
181-
let prevState = JSON.parse(ham.getAttribute('aria-expanded'))
182-
ham.setAttribute('aria-expanded', !prevState)
183-
})
184-
185-
darkToggleButtons.forEach(btn => {
186-
btn.addEventListener('click', () => {
187-
changeDarkToggleBtnIcon()
188-
189-
if (document.body.classList.contains('dark')) {
190-
document.body.classList.remove('dark')
191-
localStorage.prefsDark = 'false'
192-
} else {
193-
document.body.classList.add('dark')
194-
localStorage.prefsDark = 'true'
195-
}
196-
197-
})
198-
})
199-
</script>
200-
</body>
8+
<body></body>
2019
</html>

0 commit comments

Comments
 (0)