Re: [lojban] proposed grammar definition for ZOhOI

On Wed, Jan 26, 2011 at 10:47 PM, Ross Ogilvie <oges007@gmail.com> wrote:

The problem is if you want to allow a decimal point (or other
shorthands overloading the meaning of a symbol) then you will need to
put it in the parsing rules to figure out whether a dot is a decimal
point (only allowed in a string of PA for example) or a pause.

Straight substitution would be in adequate to handle this.

On Thursday, January 27, 2011, Alex Rozenshteyn <rpglover64@gmail.com> wrote:
> Regarding the response to the third point, couldn't you just have an exhaustive list of the shorthand transformations (wouldn't you need one anyway) and preprocess the text, transforming the shorthand to the words they represent?
>
> I feel like the biggest problem is not that of parsing.
>
> On Wed, Jan 26, 2011 at 9:36 PM, .alyn.post. <alyn.post@lodockikumazvati.org> wrote:
> On Wed, Jan 26, 2011 at 08:18:02PM -0500, Alex Rozenshteyn wrote:
>> pe'i there should be 3 ways of writing lojban:
>>
>
> After a brief brainstorm, I could support these three modes in my
> parser should that be desireable.
>
>> 1. Strict: the only characters allowed (barring alphabet shifts) are
>> lojban characters.
>
> The PEG grammar currently allows digits and some punctuation. I'd
> need to add an immediate rule when these productions are matched to
> reject those productions if strict mode was enable and forbidden
> characters appear.
>
>> 2. Visually mnemonic: characters such as quotation marks and parentheses
>> etc. are allowed to make skimming the text easier; there is no need to
>> standardize (although suggestions might be welcome) what means what
>> because the characters will be ignored (treated as whitespace) by the
>> parser, and so every spoken syllable will still need to be spelled
>> out.
>
> This is how the PEG grammar works now. I believe my parser allows
> more punctuation than camxes, which is a trivial fix should that be
> a problem.
>
>> 3. Visual shorthand: It will develop anyway, so it's best to standardize
>> it. e.g. {xu} can be *replaced* by a question mark, {to} and {to'o}
>> might be *replaced* by left and right parentheses, etc. It would make
>> sense to speak of {xubu}, the grapheme representing the cmavo {xu}
>>
>
> This would require defining what this visual shorthand was and
> modifying any rule affected. It would also require not permitting
> the defined shorthand punctuation to be whitespace.
>
> -Alan
> --
> .i ko djuno fi le do sevzi
>
> --
> You received this message because you are subscribed to the Google Groups "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
>
>
>
> --
> Alex R
>
>
> --
> You received this message because you are subscribed to the Google Groups "lojban" group.
> To post to this group, send email to lojban@googlegroups.com.
> To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.