|
Server : Apache/2.4.62 System : FreeBSD fbsdweb2.web.rcn.net 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 User : www ( 80) PHP Version : 8.3.8 Disable Function : NONE Directory : /domains/markrose/board/messages/ |
Upload File : |
<html><head><title>Sound changes</title></head>
<body bgcolor="#FFFFFF">
<center><h1><!--title-->Sound changes
</h1></center>
<hr size=7 width=75>
<p>Posted by <b><!--poster-->Gustavo S. Pereira</b>
on <!--date-->16:35 2/7/02
<p>In reply to: (none)
<!-- PUT MESSAGE HERE -->
<p>
Hi there!
<p>Well, I am attempting to devise a set of sound changes to make a new
language from another one, but it's quite difficult to start that list!!
I know the types of sound changes I can include, but what changes to
include first?? (like the transition to a medieval language, than to a
modern one). Could you give us some tips? You've made such a wonderful
work on the Cadhinor > Verdurian, Cadhinor > Ismaîn and Cadhinor >
Barakhinei sets of sound changes (specially the first one) that I would
like to hear some words from you about starting and making a sound
changes list.
<p>Regards,
<br>Gustavo Pereira
<hr><i>Mark responds:
<p>Hmm... it's hard to describe, being more of an art than a science.
<p>You have to play around a lot. Make a smallish wordlist (say, 100 words), run the program,
and edit the sound changes. Keep doing this for a long time.
<p>The order comes into play only when one change feeds another. E.g. if you want umlaut <b>and</b> final-syllable truncation, make sure you do it in that order, or the truncation rule will eliminate the input to the umlaut rule. Trial and error is enough to find such problems.
<p>A language does not know, of course, whether it's modern or medieval, and there is no sound change that's likelier at one time than another. In effect, then, you can divide up your medieval and modern rules arbitrarily. The only
guideline I'd suggest is that the rule lists be of comparable size (so the
medieval language isn't too close to either end) and be fairly diverse (so you don't have, say, just vowel changes leading to the medieval language, and just consonant changes leading to the modern language).
<p>Maybe more tricky is how many rules to include. You can use my grammars as a guideline; or just examine your results. If the wordlist looks too much like
the input, add more rules.
<p>The Verdurian list is so long because I was working with existing Cadhinor
and Verdurian lexicons. So, I often had to tailor rules to produce the words
I knew I wanted. In that way it was more like working with real languages:
you examine a bunch of words and try to figure out what sound change could
possibly account for the end results!
</i>
<hr><center>
<i>To make a reply, or see replies, see <a href="../">the index page</a>.</i>
</center>
<hr>
<!-- For index page:
<li><a href="messages/316.html">Sound changes</a> -
<b>Gustavo S. Pereira</b>
<i>16:35 2/7/02</i>
-->
</body></html>