<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/4/2019 4:32 PM, De'vID wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+7zAmO7zxySQxgw5OMi5q3ahL3EZnwC++-9SETeDoowaQOS8Q@mail.gmail.com">
<div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Nov 4, 2019, 21:59 ,
<<a href="mailto:kechpaja@kechpaja.com" target="_blank"
rel="noreferrer" moz-do-not-send="true">kechpaja@kechpaja.com</a>>
wrote:</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
It also isn't that strange for a language to have an affix
that can't <br>
attach to words with certain phonological shapes, even if
the resulting <br>
word wouldn't violate any phonological rules. For instance,
the English <br>
deadjectival verbalizing suffix "-en" that we see in words
such as <br>
"redden" and "darken" (it's generally used with color terms,
but can <br>
occasionally occur with other adjectives) cannot be added to
adjectives <br>
ending in a vowel or sonorant — which is why you don't hear
*yellowen or <br>
*greenen. </blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">You do if you're willing to embiggen your
vocabulary.</div>
</blockquote>
<p>By applying known rules in ways that don't contradict other
rules, as with the word <i>embiggen.</i> But you <i>don't</i>
hear <i>yellowen</i> or <i>greenen</i> because these contradict
the very rule that SapIr just cited. <i>Embiggen</i> violates so
such rule.<br>
</p>
<pre class="moz-signature" cols="72">--
SuStel
<a class="moz-txt-link-freetext" href="http://trimboli.name">http://trimboli.name</a></pre>
</body>
</html>