From lojban-out@lojban.org Fri Sep 27 16:56:32 2002
Return-Path: <lojban-out@lojban.org>
X-Sender: lojban-out@lojban.org
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-8_1_1_4); 27 Sep 2002 23:56:32 -0000
Received: (qmail 63773 invoked from network); 27 Sep 2002 23:56:32 -0000
Received: from unknown (66.218.66.216)
  by m14.grp.scd.yahoo.com with QMQP; 27 Sep 2002 23:56:32 -0000
Received: from unknown (HELO digitalkingdom.org) (204.152.186.175)
  by mta1.grp.scd.yahoo.com with SMTP; 27 Sep 2002 23:56:32 -0000
Received: from lojban-out by digitalkingdom.org with local (Exim 4.05)
  id 17v50r-0004uQ-00
  for lojban@yahoogroups.com; Fri, 27 Sep 2002 16:59:13 -0700
Received: from digitalkingdom.org ([204.152.186.175] helo=chain)
  by digitalkingdom.org with esmtp (Exim 4.05)
  id 17v507-0004u7-00; Fri, 27 Sep 2002 16:58:27 -0700
Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 27 Sep 2002 16:58:26 -0700 (PDT)
Received: from cs6668125-184.austin.rr.com ([66.68.125.184] ident=root)
  by digitalkingdom.org with esmtp (Exim 4.05)
  id 17v503-0004ty-00
  for lojban-list@lojban.org; Fri, 27 Sep 2002 16:58:23 -0700
Received: from cs6668125-184.austin.rr.com (asdf@localhost [127.0.0.1])
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3) with ESMTP id g8S02ZGZ030689
  for <lojban-list@lojban.org>; Fri, 27 Sep 2002 19:02:35 -0500 (CDT)
  (envelope-from fracture@cs6668125-184.austin.rr.com)
Received: (from fracture@localhost)
  by cs6668125-184.austin.rr.com (8.12.3/8.12.3/Submit) id g8S02ZHO030688
  for lojban-list@lojban.org; Fri, 27 Sep 2002 19:02:35 -0500 (CDT)
Date: Fri, 27 Sep 2002 19:02:35 -0500
To: lojban-list@lojban.org
Subject: [lojban] Re: paroi ro mentu
Message-ID: <20020928000235.GA30608@allusion.net>
References: <20020927162235.GA28708@allusion.net> <LPBBJKMNINKHACNDIIGMIEJDGJAA.a.rosta@lycos.co.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8"
Content-Disposition: inline
In-Reply-To: <LPBBJKMNINKHACNDIIGMIEJDGJAA.a.rosta@lycos.co.uk>
User-Agent: Mutt/1.4i
X-archive-position: 1651
X-ecartis-version: Ecartis v1.0.0
Sender: lojban-list-bounce@lojban.org
Errors-to: lojban-list-bounce@lojban.org
X-original-sender: fracture@allusion.net
Precedence: bulk
X-list: lojban-list
X-eGroups-From: Jordan DeLong <fracture@allusion.net>
From: Jordan DeLong <lojban-out@lojban.org>
Reply-To: fracture@allusion.net
X-Yahoo-Group-Post: member; u=116389790
X-Yahoo-Profile: lojban_out

--ibTvN161/egqYuK8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 28, 2002 at 12:33:56AM +0100, And Rosta wrote:
> jordan:
> > After the baseline ends, if there is sufficent desire for it a cmavo
> > could be created to invert tag scope, so you would say
> > ro mentu <some cmavo> paroi
> > (for all minutes once). This requires a real grammar change and
> > such though, so I don't advocate using it until/unless it were to
> > be adopted into the official grammar after the baseline.
> > (It would need to add a
> > term -> sumti <that cmavo> tag
> > rule).
>=20
> Couldn't you just use an experimental cmavo in UI?

Well you could, but it's somewhat lame. I think it would be nicer
either to preserve the order of the quantifiers by doing something
which would invert them, or to make it have its own selma'o so it
would only be allowed in the rule for terms formed from tag+sumti.

Either way it's definitely not a pressing concern that is worth
violating the baseline over: it seems to make sense that things
should still go left to right for terms made from tag+sumti, and
it can always be overidden with a prenex.

--=20
Jordan DeLong - fracture@allusion.net
lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u
sei la mark. tuen. cusku

--ibTvN161/egqYuK8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9lPGbDrrilS51AZ8RAlBEAJ9N7pQ/MyQyDV6iokxLkIfEHEbRjgCfbEMX
RiyWNy9jQUHh2KQCDNSmG3U=
=oYAU
-----END PGP SIGNATURE-----

--ibTvN161/egqYuK8--

