CONLANG Digest - 3 Nov 2000

> From:    Robert Hailman <robert@...>
> Subject: Conlangers with ICQ.
>
> If anyone else should like to, please post your ICQ contact info, or
> contact me over ICQ.
ICQ: 1936556
(AIM: MukeTurtle)

> From:    Robert Hailman <robert@...>
> Subject: Re: CONLANG Digest - 2 Nov 2000 to 3 Nov 2000 (#2000-301)
>
> > > They are complex, I can't deny. I used them in the original draft of
> > > Ajuk, but my handwriting turned them into breves and then to macrons -
> >
> > Now, an s and a z with a _macron_ would be something!
>
> I can't say I didn't like them, but I didn't even begin to think about
> typing them. I don't think Unicode has those.
No, but it does have a macron "combining character".

> > > I kand use <j> for /dZ/, I already use it for /j/, as inspired by
Polish
> > > & German.
>
> Kand? What was I thinking? I think that's supposed to be "can't".
You were probably being inspired by German ;)

> From:    Nik Taylor <fortytwo@...>
> Subject: Re: CONLANG Digest - 2 Nov 2000 to 3 Nov 2000 (#2000-301)
>
> Muke Tever wrote:
> > long, strong, wrong, and (obs.) mong
> > --> stronger /stSrANgr=/  "more strong"
> > --> wronger /rANr=/ "more wrong, one who wrongs"
> > --> longer /lANgr=/ "more long"
> > --> longer /lANr=/ "one who longs"
> > --> monger /mVNgr=/ "one who trafficks"
>
> The last of which now only exists in compounds, e.g., "warmonger",
> "fishmonger", "rumormonger".
True, but the pronunciation remains.

> Anyhoo, to be fair to Jesse, that is a good generalization, a fairly
> reliable way of knowing whether {ng} is /N/ or /Ng/, just a few minor
> changes need to be made, like that comparative and superlative suffixes
> cause the /g/ to surface, with "monger" being an exception.  It's not
> perfect, but it's a pretty reliable system.
(Add a rule for comparatives and "wronger" becomes an exception.)

[Also, for the other rule, "dinghy" and "hangar" have /N/ midmorpheme.]

     *Muke!
--
http://muke.twu.net/