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=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,T_DKIM_INVALID autolearn=no 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: Thu, 16 Dec 2010 05:57:31 -0800 Received: from chain.digitalkingdom.org ([192.168.123.127]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PTEK6-0007KF-Ge; Thu, 16 Dec 2010 05:56:46 -0800 Received: with ECARTIS (v1.0.0; list jbovlaste); Thu, 16 Dec 2010 05:55:48 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1PTEJ8-0007K7-6w for jbovlaste-real@lojban.org; Thu, 16 Dec 2010 05:55:46 -0800 Received: from nm2-vm0.bullet.mail.ac4.yahoo.com ([98.139.52.66]) by chain.digitalkingdom.org with smtp (Exim 4.72) (envelope-from ) id 1PTEJ1-0007Jw-UV for jbovlaste@lojban.org; Thu, 16 Dec 2010 05:55:46 -0800 Received: from [98.139.52.190] by nm2.bullet.mail.ac4.yahoo.com with NNFMP; 16 Dec 2010 13:55:33 -0000 Received: from [98.139.52.163] by tm3.bullet.mail.ac4.yahoo.com with NNFMP; 16 Dec 2010 13:55:33 -0000 Received: from [127.0.0.1] by omp1046.mail.ac4.yahoo.com with NNFMP; 16 Dec 2010 13:55:33 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 866165.87645.bm@omp1046.mail.ac4.yahoo.com Received: (qmail 11666 invoked by uid 60001); 16 Dec 2010 13:55:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1292507733; bh=yiZDGIMe9HMlvKaNKcEVdWCVEG5mQaXgfF2Qj8XtFEs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=opB7QKd7eYcvmRyC6cM7RZLwrEC7fScVORiH/hFb467x3oQ1+o6cEUX8JST+tn/woX/CiL/FkxK8wR+1uGwu1ReeNXoN1HhOR9XCf9A+eTXwuMPK8Q22BaSGwM9gUVdRDdKRvs7xvtDDPB3Jz8KnUKHsKuq9/P9bXTDrnmr3PBk= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=D7j21sxEYafmr5jpkICgEEqkM11Bb9wyFzyWqOh+4w3woMQqywEJ0FH5iCWry5ZHsc4E2J15Vxk167g4i9a8C2pjHXUCBbcDOwoYn7bBPkF7GdfX4vfg42vJBUwuvf0qHbMXF/XeKeUzjH0vkqKhR6HE+N5dXnRZ6CwPNJwnbc4=; Message-ID: <671046.10882.qm@web88001.mail.re2.yahoo.com> X-YMail-OSG: L_CzbdkVM1kCdcX0ZZbSCylVIQxueWUdKQ2Mis.A_SxQC92 rvZboFMUSmR_WDKzV3R5ea5WKJ8HuxlsWa0x2zU0xd5ZxSSi_T8dMeGgVBWL IZotC2O5diOsrXOTbNgiFfnyS5AVkhuuD9TwnJ0PpmUnLj7cELio9_y86STk z8ZSnzInYjnLEGAlbWdHbKHzywlOKXKEqDeQpZ.6ycDyjkyPUgwKRsuTaW7Y ApuzqPw.YvxMlwQHrnlhEFmbktRnov55.BSXYLrW.6w6o8THD1zNB1VVlxRk PegAqKVMK3mGJNC9L8nRuhdiLjkCRKzeUjUZG4LNEjb3KEnZA4oqqDgSBNiT y0.sL4cEDY7QfHuN.eVsdi3cMEcK8aJdJVM9of7pQPMXDBGF56bAwql1Z9N_ 8P7G1OFZwsVME Received: from [99.240.58.72] by web88001.mail.re2.yahoo.com via HTTP; Thu, 16 Dec 2010 05:55:33 PST X-Mailer: YahooMailRC/553 YahooMailWebService/0.8.107.285259 References: <143260.7676.qm@web88005.mail.re2.yahoo.com> <201012141326.05329.phma@phma.optus.nu> <758400.4191.qm@web88008.mail.re2.yahoo.com> <821066.98318.qm@web88008.mail.re2.yahoo.com> Date: Thu, 16 Dec 2010 05:55:33 -0800 (PST) From: "A. PIEKARSKI" Subject: [jbovlaste] Re: Alice in Wonderland nix To: jbovlaste@lojban.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: totus@rogers.com Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste Content-Length: 2244 Lines: 96 >{nanl} could also work. Maybe it's best for the long run rule (assuming any >consonant pair can be properly pronounced at the end of a word). I don't think it can.  It's barely distinguishable for {nan}. totus > >Like I said, I think it's more important to decide on a rigid rule than try to >maintain some apparent symmetry (that obviously wasn't very apparent to anyone >here). > >I believe there are more titles than what has been up-to-now presented, and >their number can keep growing in the future as titles evolve, so you can't rely >on symmetry to always be available. > >Some more titles: >"sir/madam" - perhaps {nol} (or {nolnim} and {nolnaun} if you want gender >specifics) >"judge" - {paip} >"captain" - {ja'aj} >etc... > > >On Thu, Dec 16, 2010 at 2:41 AM, Michael Turniansky >wrote: > >I have no problem with syllabic "L", so don't mind "nanl". >>   --gejyspa >> >> >> >>On Wed, Dec 15, 2010 at 2:18 PM, A. PIEKARSKI wrote: >>> >>>>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}. >>> >>> If we use {naun} for 'Mr.' then we can use {naux} for >>> Master.  Symmetry preserved! >>> >>> totus >>> >>>>> >>>>>> >>>>>> > 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 >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >>> >> >> >> >> >