Received-SPF: pass (google.com: domain of tsani@mail.jerrington.me designates 192.99.166.45 as permitted sender) client-ip=192.99.166.45;
Message-ID: <55A6A80B.1020801@mail.jerrington.me>
Date: Wed, 15 Jul 2015 14:35:55 -0400
From: Jacob Thomas Errington <tsani@mail.jerrington.me>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: lojban@googlegroups.com
Subject: Re: [lojban] Re: {tu'e...tu'u} in NU
References: <a9475bfd-ac16-40ce-bb60-7b2a057a681d@googlegroups.com> <d73e2a72-cb9e-495d-9dc5-3e22878a41c2@googlegroups.com> <196303dc-9717-45a5-a521-788aa2a153f8@googlegroups.com>
In-Reply-To: <196303dc-9717-45a5-a521-788aa2a153f8@googlegroups.com>
Content-Type: multipart/alternative;
 boundary="------------070101040007030601010207"
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
X-Spam_score: -3.0
X-Spam_score_int: -29
X-Spam_bar: ---

This is a multi-part message in MIME format.
--------------070101040007030601010207
Content-Type: text/plain; charset=UTF-8; format=flowed

On 07/15/2015 09:51 AM, la durka wrote:
> In general I think it's a bad idea to change {.i} so that it doesn't 
> always start a new sentence. The major problems are that it deals a 
> heavy blow to the whole concept of elidible terminators, if you can't 
> "just start a new sentence" to get out of a deeply nested pit of 
> abstractions; and it means it's no longer possible to quickly scan a 
> text for {.i} to separate the sentences -- you need to parse the 
> entire text to find the sentence boundaries.
We can't really just scan the text for {.i} as it may be quoted, 
specifically by {lu...li'u}. Indeed, lu-quotes already form a construct 
that creates a new "level zero" for sentences; giving us this 
flexibility in any bridi context would merely act as a generalization of 
this existing capability.

That said, I'm in favour of allowing tu'e..tu'u within NU, and really, 
at the beginning of any bridi.

.i mi'e la tsani mu'o

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--------------070101040007030601010207
Content-Type: text/html; charset=UTF-8

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 07/15/2015 09:51 AM, la durka wrote:<br>
    <blockquote
      cite="mid:196303dc-9717-45a5-a521-788aa2a153f8@googlegroups.com"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">In general I think it's a bad idea to change {.i}
        so that it doesn't always start a new sentence. The major
        problems are that it deals a heavy blow to the whole concept of
        elidible terminators, if you can't "just start a new sentence"
        to get out of a deeply nested pit of abstractions; and it means
        it's no longer possible to quickly scan a text for {.i} to
        separate the sentences -- you need to parse the entire text to
        find the sentence boundaries.<br>
      </div>
    </blockquote>
    We can't really just scan the text for {.i} as it may be quoted,
    specifically by {lu...li'u}. Indeed, lu-quotes already form a
    construct that creates a new "level zero" for sentences; giving us
    this flexibility in any bridi context would merely act as a
    generalization of this existing capability.<br>
    <br>
    That said, I'm in favour of allowing tu'e..tu'u within NU, and
    really, at the beginning of any bridi.<br>
    <br>
    .i mi'e la tsani mu'o<br>
  </body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:lojban+unsubscribe@googlegroups.com">lojban+unsubscribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href="mailto:lojban@googlegroups.com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href="http://groups.google.com/group/lojban">http://groups.google.com/group/lojban</a>.<br />
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br />

--------------070101040007030601010207--