Return-path: X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on chain.digitalkingdom.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS, T_DKIM_INVALID,T_TO_NO_BRKTS_FREEMAIL autolearn=ham version=3.3.1 X-Spam-Personal-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on chain.digitalkingdom.org Envelope-to: rlpowell@digitalkingdom.org Delivery-date: Wed, 15 Dec 2010 08:09:17 -0800 Received: from chain.digitalkingdom.org ([192.168.123.127]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PStu0-0006qy-F0; Wed, 15 Dec 2010 08:08:28 -0800 Received: with ECARTIS (v1.0.0; list jbovlaste); Wed, 15 Dec 2010 08:07:27 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1PStt0-0006pU-Ce for jbovlaste-real@lojban.org; Wed, 15 Dec 2010 08:07:26 -0800 Received: from mail-vw0-f53.google.com ([209.85.212.53]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PStsw-0006iP-Dl for jbovlaste@lojban.org; Wed, 15 Dec 2010 08:07:26 -0800 Received: by vws8 with SMTP id 8so838399vws.40 for ; Wed, 15 Dec 2010 08:07:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=4ixwyB/16tOxPV8cpMf65pHX7+IM4RQke3UbuyAEKx8=; b=hWbFkGGogPqwH7AP4UiClwXrSrkILucfRYrdtaOnEbt0dumVsKxH5BlSZrEdJKDAYz uKCqeZbSgNwLjlu0UGhHFz2dbc0E3x4qddCfwwr+bD6YWDoBPY9NvTixJ16V695yYSPS pQ+grC6DjOufESllqIuT5y2alkC4sVBcTU7nA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=i3U0azAahu2RqZFdGV3lOpkD9lebgS2WQl00r5GSg/s7jcp5hDoZw/6wiAZ8fshruH 1vfRwDSdQlFirBEE+1itil50jCG+at4T0We8iATDImpykmoUTVLz+YlDIUiGHFP+u4tu Hbi2v0zqxbKf5N0UourjUxUR2YsZc9RtU2Xnc= MIME-Version: 1.0 Received: by 10.229.2.97 with SMTP id 33mr613069qci.288.1292429235913; Wed, 15 Dec 2010 08:07:15 -0800 (PST) Received: by 10.229.48.14 with HTTP; Wed, 15 Dec 2010 08:07:15 -0800 (PST) In-Reply-To: <758400.4191.qm@web88008.mail.re2.yahoo.com> References: <143260.7676.qm@web88005.mail.re2.yahoo.com> <201012141326.05329.phma@phma.optus.nu> <758400.4191.qm@web88008.mail.re2.yahoo.com> Date: Wed, 15 Dec 2010 18:07:15 +0200 Message-ID: Subject: [jbovlaste] Re: Alice in Wonderland nix From: "Aviv S." To: jbovlaste@lojban.org Content-Type: multipart/alternative; boundary=0014853bc6e08104530497752111 X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: seraviv@gmail.com Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste Content-Length: 3704 Lines: 101 --0014853bc6e08104530497752111 Content-Type: text/plain; charset=ISO-8859-1 I see. I still think {nax} is a confusing choice given its rafsi association. I think, given the lack of a short rafsi for {nanla} we could resort to: {nanlal}. It's just two syllables, and most english titles have two syllables as well. In any case, it's still shorter than {la noi nanla neim}. Also, I dont think the symmetry should be reserved just for the sake of {nan}. You may eventually end up with more and more titles, and better to stick with the {shortest rafsi + last consonant} formation then try to balance symmetry for them all IMO. On Wed, Dec 15, 2010 at 4:12 PM, A. PIEKARSKI wrote: > > > > > > > So I propose also these rafsi-based cmevle: > > > > > > {nim} for Ms. > > > Since no rafsi are available for Mr. and Master, > > > I propose: > > > > > > {nax} for Master > > > {nan} for Mr. > > How about {naur}? What's {nax} from, besides the > > North Caucasus? > > > > The reason I chose {nax} and {nan} was to provide some > symmetry - although I don't feel that strongly about it. > > .nix. (Miss) > .nax. (Master) > .nan. (Mister) > .nim.(Ms) > Aviv, the meaning of 'Master' here is the male counterpart of 'Miss'. > Not much used in English these days, but it is used in other > languages. > > Using short rafsi as a base was a fine idea, but we can't stick to it > too religiously. {nanla} doesn't have a short rafsi, so {nax} was an > obvious choice. > > totus > > > > --0014853bc6e08104530497752111 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I see.
I still think {nax} is a confusing choice given its rafsi association.=
I think, given the lack of a short rafsi for {nanla} we could resort t= o:
{nanlal}.
It's just two syllables, and most english titles have two syllable= s as well.
In any case, it's still shorter than {la noi nanla neim}.
=A0
Also, I dont think the symmetry should be reserved just for the sake o= f {nan}. You may eventually end up with more and more titles, and better to= stick with the {shortest rafsi + last consonant} formation then try to bal= ance symmetry for them all IMO.

On Wed, Dec 15, 2010 at 4:12 PM, A. PIEKARSKI <totus@rogers.com> wrote:


>
> > So I propose also these rafsi-b= ased cmevle:
> >
> > {nim} for Ms.
> > Since no rafsi are available for Mr. and Master= ,
> > I propose:
> >
> > {nax} for Master
>= ; > {nan} for Mr.

How about {naur}? What's {nax} from, besides the
&= gt; North Caucasus?
>

The reason I chose {nax} and {nan}= was to provide some
symmetry - although I don't feel that strongly = about it.

.nix. (Miss)
.nax. (Master)
.nan. (Mister)
.nim.(Ms) =A0
Av= iv, the meaning of 'Master' here is the male counterpart of 'Mi= ss'.
Not much used in English these days, but it is used in other languages.
=A0
Using short rafsi as a base was a fine idea, but we ca= n't stick to it
too religiously.=A0 {nanla} doesn't have a short= rafsi, so {nax} was an
obvious choice.
=A0
totus



<= /blockquote>

--0014853bc6e08104530497752111--