From pycyn@aol.com Wed Mar 14 08:55:34 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_0_4); 14 Mar 2001 16:55:34 -0000 Received: (qmail 21049 invoked from network); 14 Mar 2001 16:55:33 -0000 Received: from unknown (10.1.10.27) by l10.egroups.com with QMQP; 14 Mar 2001 16:55:33 -0000 Received: from unknown (HELO imo-r19.mx.aol.com) (152.163.225.73) by mta2 with SMTP; 14 Mar 2001 16:55:32 -0000 Received: from Pycyn@aol.com by imo-r19.mx.aol.com (mail_out_v29.5.) id r.80.81ef355 (6621) for ; Wed, 14 Mar 2001 11:55:15 -0500 (EST) Message-ID: <80.81ef355.27e0fc72@aol.com> Date: Wed, 14 Mar 2001 11:55:14 EST Subject: Re: [lojban] Numbers To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_80.81ef355.27e0fc72_boundary" Content-Disposition: Inline X-Mailer: AOL 6.0 for Windows US sub 10501 From: pycyn@aol.com --part1_80.81ef355.27e0fc72_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 3/14/2001 5:49:28 AM Central Standard Time, cowan@ccil.org writes: > if it's in a context, you are asking for a digit or whatever fits in that > context. > > All the question words work that way.> > So, {xo} floating freely (i.e., not in a string of PA) can take any PA-string as an answer (well, any that have currently got accepted or being tested interps). In a PA string, it is asking for an appropriate replacement, presumably a digit (or suchlike, if we allow Lojbab's -- and cowan's? -- strangenesses). So, for example, {xonono} "How many hundreds" Clearly, {no,..., so} are appropriate answers. What about {reci}? What, even more trickily, about {nosobi} "We didn't get to 100, even; 98"? I think the answer here is always "Yes". Similarly, {xo ki'o} asks how many thousands but could be answered {nosomuze}. I do think that in the middle of a string, only a digit works: {muxovo} can only take {no...so} and similarly {xamuxo}. On the other hand, at the end of a string of {no} I think the interval opens up again: {panoxo} is "a hundred and what?" and so {zere} is permissible, blotting out the {no} in the process. (And, of course, {nozere} -- "What 100, we only got 72.") Does this sound about right? --part1_80.81ef355.27e0fc72_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 3/14/2001 5:49:28 AM Central Standard Time, cowan@ccil.org
writes:



<It works both ways.  If xo is standalone, you are asking for any number;
if it's in a context, you are asking for a digit or whatever fits in that
context.

All the question words work that way.>



So, {xo} floating freely (i.e., not in a string of PA) can take any PA-string
as an answer (well, any that have currently got accepted or being tested
interps).
In a PA string, it is asking for an appropriate replacement, presumably a
digit (or suchlike, if we allow Lojbab's -- and cowan's? -- strangenesses).  
So, for example,
{xonono} "How many hundreds" Clearly, {no,..., so} are appropriate answers.  
What about {reci}?  What, even more trickily, about {nosobi} "We didn't get
to 100, even; 98"?  I think the answer here is always "Yes".  Similarly, {xo
ki'o} asks how many thousands but could be answered {nosomuze}.  I do think
that in the middle of a string, only a digit works: {muxovo} can only take
{no...so} and similarly {xamuxo}.
On the other hand, at the end of a string of {no} I think the interval opens
up again:
{panoxo} is "a hundred and what?" and so {zere} is permissible, blotting out
the {no} in the process.  (And, of course, {nozere} -- "What 100, we only got
 72.")
Does this sound about right?
--part1_80.81ef355.27e0fc72_boundary--