The Jargon File, Version 4.2.2, 20 Aug 2000 by Various
page 54 of 1403 (03%)
page 54 of 1403 (03%)
![]() | ![]() |
|
many varieties of southern American will automatically map /o/ to
/aw/; and so forth. (Standard American makes a good reference dialect for this purpose because it has crisp consonants and more vowel distinctions than other major dialects, and tends to retain distinctions between unstressed vowels. It also happens to be what your editor speaks.) Entries with a pronunciation of `//' are written-only usages. (No, Unix weenies, this does not mean `pronounce like previous pronunciation'!) _________________________________________________________________ Node:Other Lexicon Conventions, Next:[162]Format for New Entries, Previous:[163]Pronunciation Guide, Up:[164]Top Other Lexicon Conventions Entries are sorted in case-blind ASCII collation order (rather than the letter-by-letter order ignoring interword spacing common in mainstream dictionaries), except that all entries beginning with nonalphabetic characters are sorted after Z. The case-blindness is a feature, not a bug. The beginning of each entry is marked by a colon (:) at the left margin. This convention helps out tools like hypertext browsers that benefit from knowing where entry boundaries are, but aren't as context-sensitive as humans. In pure ASCII renderings of the Jargon File, you will see {} used to bracket words which themselves have entries in the File. This isn't |
|