-
Notifications
You must be signed in to change notification settings - Fork 2
/
faq.php
595 lines (595 loc) · 20.4 KB
/
faq.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
<?php require_once ('titletop.php');
require_once ('navheaderside.php'); ?>
<div class="Content">
<span style="font-weight: bold;"><span style="font-weight: bold;"><span
style="font-weight: bold;">FAQ:<br>
<a href="#whomade">Who made this?</a><br>
<a href="#feedback">Can I provide feedback?</a><br>
<a href="#contact">How can I contact you?</a><br>
<a href="#register">Do I need to register or log in to use ELDER?</a></span><br>
<br>
How-to: How do I...<br>
<a href="#gloss">Gloss a sentence?</a><br>
<a href="#tones">Add tones for a sentence?</a><br>
<a href="#vowels">Standardize my vowels?</a><br>
<a href="#consonants">Standardize my consonants?</a><br>
<a href="#syltype">Format "syllable type"?</a><br>
<a href="#audio"><span style="font-weight: bold;">Encode my audio files?</span></a><br>
<a href="#metadata">Add metadata to my audio files?</a><br>
<a href="#naming">Name my audio files?</a><br>
<br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="whomade"></a>Who made this?<br>
<br>
</span></span></span>ELDER was designed by Anna Belew for her master's
thesis in the Boston University Program for Applied Linguistics.
It was programmed pro bono by Connor Shaughnessy using Notepad++ and
MySQL. ELDER is based
on a FileMaker layout by Cathy O'Connor and Amy Rose Deal. <br>
<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="feedback"></a>Can I
provide feedback?<br>
<br>
</span></span></span>ELDER's improvement depends on you and your
feedback! If you discover bugs, notice faulty design, or have
ideas for features you'd like to see, please <a
href="mailto:anna.belew@gmail.com">
let us know!</a><br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="contact"></a>How can I
contact you?<br>
<br>
<span style="font-weight: bold;"></span></span>I'm happy to help out
with any questions or problems. Email me at
<a href="mailto:anna.belew@gmail.com">anna.belew@gmail.com</a> <span
style="font-weight: bold;"><span style="font-weight: bold;"></span><br>
</span><br>
<span style="font-weight: bold;"><span style="font-weight: bold;"><span
style="font-weight: bold;"></span><br>
<br>
<br>
<br>
<a name="register"></a>Do I need to register or log in to use ELDER?<br></span></span>
<br>
Short answer: No. However, to preserve
the hard work of its users, ELDER does not allow casual modification or deletion of data by anyone other than the person who entered it.
So, if you've contributed something but need to change or get rid of it, you must <a href="/register.php">register</a> and/or <a href="/login.php">log in</a>.
If you haven't entered any data yet, your name won't appear on the registration screen, but nor do you have any need to register! Anyone can look around or create new entries
without logging in.<br>
<br>
<br>
<br>
<br>
<br>
<big><big><span style="font-weight: bold;">How do I....</span></big></big><br>
<br>
<br>
<a name="gloss"></a>Gloss a sentence?<br>
<br>
</span></span>The <span style="text-decoration: underline;">free
translation</span> is simply a rough translation into English; for
example, the free translation of /mə jən busi gi/ would be "Did I see
the cat?" rather than "I saw cat question." It's meant to convey
the general meaning of an utterance rather than the details.<br>
<br>
The <span style="text-decoration: underline;">close gloss</span> is a
more detailed representation of the sentence. The <span
style="text-decoration: underline;">close gloss</span> should
represent not only an English translation of the word, but any details
about case, number, tense, etc. for a given word. The database
reads spaces in the gloss line as meaning word breaks, so don't put
spaces in the gloss for a single word; use hyphens if you need to gloss
something as more than one word. For example, /mə jən kwitʃɯ gi/
would have a close gloss something like this:<br>
<br>
mə
jən
kwitʃɯ
gi<br>
1p-sg-nom
see-pst1
tree-parasite question marker<br>
<br>
And would be entered into the close gloss box as:<br>
<br>
1p-sg-nom see-pst1 tree-parasite question-marker<br>
<br>
<span style="font-weight: bold;">If you're not sure exactly what
something is</span>, leave it blank rather than guessing. Just
<span style="font-weight: bold;">put a question mark in place of a gloss</span>,
using the same
spaces-between-words convention. ELDER will then show a blank
space for that word in the close gloss. For example:<br>
<br>
tʃaŋmvunʒu mi kɔ arian nɛnɑ <br>
evening-meal ? then Ariane go-pst1<br>
<br>
For the sake of consistency, please see the tense table and
noun/pronoun table so that we're all using the same standardized
abbreviations.<br>
<br>
<br>
<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
<br>
<br>
<a name="tones"></a>Add tones for a sentence?<br>
</span></span><br>
Keep in mind that the <span style="text-decoration: underline;">analyzed
tone</span> and <span style="text-decoration: underline;">sentence-level
pitch</span> are different things. <span
style="text-decoration: underline;">Analyzed tone</span> would be your
phonological breakdown of the pitch into H and L tones. If you
haven't taken phonology, don't worry about this part; just record the
sentence-level pitch as best you can.<br>
<br>
The syntax for inputting <span style="text-decoration: underline;">sentence-level
pitch</span> is pretty simple: insert
a semicolon to represent word breaks, and a comma to represent syllable
breaks. So if we have the following sentence:<br>
<br>
3 5
2͡3 2 1<br>
mɛnzwi swɛn kolo<br>
<br>
We'd input the tone as 3,5;23;2,1 in the text box.<span
style="font-weight: bold;"> </span><span
style="font-weight: bold;"></span>We know that the average linguist
doesn't want to deal with complex syntax when using a tool (unless you
love using LaTeX). Someday we'll have a more
intuitive input system-- stay tuned.<span style="font-weight: bold;"></span><span
style="font-weight: bold;"><br>
<br>
<span style="font-weight: bold;"></span></span>To add <span
style="text-decoration: underline;">analyzed tone</span> for a sentence<span
style="font-weight: bold;"></span>, don't worry about syntax; we
haven't decided on a good way to feed underlying tones to the database
yet. Just input any string of text, using standard phonological
markup for downstep (e.g. !H or ↓H)<br>
<span style="font-weight: bold;"></span><span style="font-weight: bold;"><br>
<br>
<br>
<span style="font-weight: bold;"><a name="vowels"></a>Standardize my
vowels?<br>
<br>
<span style="font-weight: bold;"></span></span></span>At the moment,
we've agreed to use the following vowel inventory:<br>
<br>
<span style="font-weight: bold;"><span style="font-weight: bold;"><span
style="font-weight: bold;"></span></span></span>
<table style="text-align: left; width: 256px; height: 167px;" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="vertical-align: top;">i<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><big><big><big>ɯ</big></big></big>
u<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">ə<br>
</td>
<td style="vertical-align: top;">o<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;">ɛ<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">ɔ<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><big><big><big>ɐ</big></big></big><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;">a<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
</tbody>
</table>
<span style="font-weight: bold;"><span style="font-weight: bold;"> <br>
</span></span>If you disagree, think we should add, remove, or change a
vowel, or have questions about the vowel inventory, <a
href="mailto:anna.belew@gmail.com">contact me</a>.<br>
<span style="font-weight: bold;"><br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="consonants"></a>Standardize
my consonants?<br>
<br>
</span></span>I've been using the following consonant inventory to
represent Medumba:<br>
<br>
<table style="text-align: left;" border="1" cellpadding="2"
cellspacing="2">
<tbody>
<tr>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top; text-align: left;"><small>Bilabial<br>
</small></td>
<td style="vertical-align: top;"><small>Labiodental<br>
</small></td>
<td style="vertical-align: top;"><small>Dental<br>
</small></td>
<td style="vertical-align: top;"><small>Alveolar<br>
</small></td>
<td style="vertical-align: top;"><small>Postalveolar<br>
</small></td>
<td style="vertical-align: top;"><small>Retroflex<br>
</small></td>
<td style="vertical-align: top;"><small>Palatal<br>
</small></td>
<td style="vertical-align: top;"><small>Velar<br>
</small></td>
<td style="vertical-align: top;"><small>Uvular<br>
</small></td>
<td style="vertical-align: top;"><small>Pharyngeal<br>
</small></td>
<td style="vertical-align: top;"><small>Glottal<br>
</small></td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Stop<br>
</small></td>
<td style="vertical-align: top;">p b<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">t d<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">k g<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">ʔ<br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Nasal<br>
</small></td>
<td style="vertical-align: top;">m<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">n<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">ŋ<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Trill<br>
</small></td>
<td style="vertical-align: top;">ʙ<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Tap or Flap<br>
</small></td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Fricative<br>
</small></td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">f v<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">s z<br>
</td>
<td style="vertical-align: top;">ʃ ʒ<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">x ɣ<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Lateral fricative<br>
</small></td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Approximant<br>
</small></td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">j<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
<tr>
<td style="vertical-align: top;"><small>Lateral approximant<br>
</small></td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;">l<br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
<td style="vertical-align: top;"><br>
</td>
</tr>
</tbody>
</table>
<br>
And, of course, [w]. <br>
<br>
Other important things:<span style="font-weight: bold;"> enter
affricates as two separate characters</span>. Use tʃu, not
ʧu. This will help make everyone's entries consistent.<br>
<br>
<span style="font-weight: bold;">Don't use diacritics as part of the
main IPA entry for words or sentences</span>; put them in the "spoken
form." We've found no evidence that Medumba has phonemic
nasalization, dentalization, etc., and diacritics make it harder to
search accurately.<br>
<br>
<br>
<span style="font-weight: bold;"><span style="font-weight: bold;"></span><br>
<br>
<br>
<span style="font-weight: bold;"><a name="syltype"></a>Format "syllable
type"</span>?<br>
<br>
</span>"Syllable type" is pretty basic at the moment-- the only segment
types it's concerned with are nasals (N), consonants (C) and vowels
(V). Don't go all super-phonologist and start inputting /mvɛl/ as
Nasal Fricative Vowel Liquid. Just stick with N, C, and V.<br>
<span style="font-weight: bold;"><br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="audio"></a>Encode my audio
files?<br>
<br>
</span></span>Short answer: make them as high-quality as
possible. Work with, at minimum, a sampling rate of 44.1 kHz and
bit-depth of 16. I don't know a ton about audio encoding, so
consider this section "under construction" until I do. Until
then, see <a href="http://emeld.org/school/classroom/audio/index.html">what
E-MELD
has
to
say
about
it</a>.<br>
<span style="font-weight: bold;"><span style="font-weight: bold;"></span><br>
<br>
<br>
<br>
<br>
<span style="font-weight: bold;"><a name="metadata"></a>Add metadata to
my audio files?</span></span><span style="font-weight: bold;"><br>
<br>
</span>Metadata is "data about data"-- in the case of language
documentation audio files, it helps keep track of who was involved in a
session, when it was, and what was discussed in the session.<br>
<br>
To add metadata to an mp3 file, it's easiest to use your usual media
player-- iTunes and Windows Media Player both allow users to create and
edit mp3 metadata. Simply use your media player to open the file
you want to tag,
right-click it, and select "get info" (or something similar). It
will bring up a window that should have an "Info" tab, complete with a
box for comments. All your metadata goes in that box. <br>
<br>
To add metadata to a WAV file, you're looking at a lot more work-- WAV
files don't actually support metadata embedding. You'll need to
find a metadata editor that adds a chunk of data in a different
format. I recommend just uploading MP3s to ELDER for now.<br>
<br>
What you should include in your metadata:<br>
<br>
Take a look at <a
href="http://emeld.org/school/classroom/metadata/bp-metadata.html">E-MELD's
guidelines
on
OLAC
metadata
standards.</a> Include as much of
that stuff as you can, but at a minimum, include your name, the
consultant's name, the name of the language you're working on, what the
file is about, what format the file is, and the date it was
created. An example metadata tag:<br>
<br>
Creator: Anna Belew<br>
Contributors: Ariane Ngabeu<br>
Language: Medumba,<a
href="http://www.ethnologue.com/14/show_language.asp?code=BYV"> byv</a><a
href="ttp://www.ethnologue.com/show_language.asp?code=byv">,</a>
Bangangte<br>
Coverage: Relative clause structures<br>
Date: 09/28/2009<br>
Format: mp3<br>
Comments: Blah blah blah here's what I have to say about this file.<br>
<br>
<br>
<br>
<span style="font-weight: bold;"><br>
<span style="font-weight: bold;"><a name="naming"></a>Name my audio
files?<br>
</span></span><br>
For now, use the following system:<br>
<br>
<span style="font-style: italic;">Naming individual files: </span><br>
<br>
[your name] plus a six-digit number-- for example, Andrei might upload
Andrei000001, Andrei000002, up through Andrei000125. It doesn't
really matter if they're consecutive, this is more for your
organization than anything else.<br>
<br>
<span style="font-style: italic;">Naming session files:</span><br>
<br>
Session files (the unedited recordings of your elicitation sessions)
should be named by their date, your name, and which chunk of the
session they are. For example, if Katie has a one-hour
elicitation session on April 10, 2010, broken up into four 15-minute
files, she'd name the files like this:<br>
<br>
Katie041010a.mp3<br>
Katie041010b.mp3<br>
Katie041010c.mp3<br>
Katie041010d.mp3<br>
<br>
This system helps us keep track of when sessions were held, and with
whom, in case the metadata is somehow lost.<br>
<br>
<br>
</body>
</div>
<?php
require_once('footer.php');
?>