On Mon, Dec 02, 2002 at 07:02:33PM -0000, And Rosta wrote:
> Jordan:
> > On Mon, Dec 02, 2002 at 11:04:47AM -0000, And Rosta wrote:
> > > Avoiding making mex harder to use is not a good reason for not making the
> > > rest of the language easier to use. I am proposing (and I think Jordan is
> > > too) that mex and other stuff that has never seen substantial usage be
> > > made more longwinded so that future generations of fluent lojbanists can
> > > decide where shortwindedness can most efficaciously be applied
> >
> > I don't support touching any of mex (unless lau/tei is considered
> > mex). I support And's *idea* here, but not the exact method by
> > which he wants to implement it. I think it is sufficent to add new
> > assignments for one or two 0-usage monosyllabic cmavo without
> > revoking their own assignemnts, and to refrain from using monosyllabic
> > xVV space
>
> How does the new-assignments-without-revoking-old work?
We assign lau'oi to selma'o LAU, with the exact meaning of lau.
We assign tei'oi to selma'o TEI, with the exact meaning of tei.
A statement is made that "lau'oi" and "tei'oi" should be used in
stead of "lau" and "tei", because lau and tei may be reclaimed in
the distant future for their monosyllabicness.
However, since no one but me supports this more moderate approach
to this, and the whole point would be to try to make both you and
everyone else happy about future Zipf possibilites, I'm pretty much
going to have to abandon it and go with everyone else in the view
that we should not worry about Zipf at all.
> > [...]
> > > > >and instead
> > > > >simply say that the mini-dictionary fixes the meaning of the cmavo it
> > > > >lists. A proper syntactic parser should not have the mahoste built
> > > > >in to it, but should instead take input from a community-maintained
> > > > >mahoste that can be updated with cmavo not listed in the mini-dictionary
> > > >
> > > > Then write one
> > >
> > > I have (collaboratively) written one for cmavo that are not in the
> > > official mahoste. It is on the wiki. It is easily adaptable (with
> > > about 1 minute's work) by anyone writing a parser to take input from
> > > a mahoste
> >
> > Erm. Lojbab was suggesting you write that parser. ;P
>
> Was he? I don't have the skills to write a parser, and I'm surprised
> Lojbab thought I did.
It was sarcasm.
Anyway, you certainly could learn what you needed to know to write
a parser (or rather to hook up to a yacc-generated parser---would
be an interesting project to rewrite the grammar for LL(1) parsing
though) if you felt like it.
I find some interest in having a parser support querying the user
(or perhaps a file in their home directory) for selma'o of bad cmavo
(and this could probably be hacked onto the jbofi'e lexer without
too much trouble).
As Nick said, If you want something done, you probably have to do
it yourself. If not, then you really shouldn't complain about what
the current parsers support.
--
Jordan DeLong - fracture@allusion.net
lu zo'o loi censa bakni cu terzba le zaltapla poi xagrai li'u
sei la mark. tuen. cusku
Attachment:
pgp00307.pgp
Description: PGP signature