Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c03::233 as permitted sender) client-ip=2a00:1450:400c:c03::233;
MIME-Version: 1.0
Date: Wed, 6 Aug 2014 11:29:07 +0400
Message-ID: <CAO7bV+jQREUbvtq4jjW9MEz3DQH6igC+huEnN42kB8xz3y1x8Q@mail.gmail.com>
Subject: [lojban] Splicing time intervals as a new sumti type
From: Gleki Arxokuna <gleki.is.my.name@gmail.com>
To: lojban@googlegroups.com
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d0444808d6cbc0804fff0edac
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -

--f46d0444808d6cbc0804fff0edac
Content-Type: text/plain; charset=UTF-8

In Lojban there is no universal method of saying:
this hour, this morning, today, next day, tomorrow, next hour.

Ofc. we have {bavlamdei} but they have the same problem as {PAmei}, namely,
you can't extract the number of time periods that the necessary segment is
apart from the referenced one.
E.g. "the day before yesterday" is definitely connected with the number 2
(or 3 if you count starting from today) however there is no way to extract
this 2 from a lujvo meaning "the day before yesterday" (like
{pruprulamdei}).

We can't use {za} either. If it's 23:00 then tomorrow is not {baza lo djedi
be li pa} because tomorrow starts in only one hour.

So here we have a different concept of splitting time.
Unlike {cacra}, {djedi}, {nanca} that split the time into intervals of a
fixed length (that can even overlap)
such concepts as "tomorrow", "this hour" split time into spliced (put in
order end to end) intervals by default from midnight for "day", the
beginning of the year (e.g. January 1) for "month" etc.

One workaround is {ca lo 2001moi nanca}, which is cheating since it's not
stated that those one-year time intervals don't overlap. Other methods like
cmevla for names of years described in L4B share the same problem with
{cabdei}, {bavlamdei}.

What is more, I found a bunch of gismu that have this splicing interval
sumti type:
cerni1 (cerni = x1 is a morning of day x2 ...)
citsi
crisa
critu
donri
dunra
murse
nicte
temci
vanci
vensa
So I suggest that we use either a cmavo or a jvajvo-generating prefix for
{djedi}, {cacra} ... to change to splicing intervals when we need them.

-- 
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.

--f46d0444808d6cbc0804fff0edac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In Lojban there is no universal method of saying:<br><div>=
this hour, this morning, today, next day, tomorrow, next hour.</div><div><b=
r></div><div>Ofc. we have {bavlamdei} but they have the same problem as {PA=
mei}, namely, you can&#39;t extract the number of time periods that the nec=
essary segment is apart from the referenced one.</div>
<div>E.g. &quot;the day before yesterday&quot; is definitely connected with=
 the number 2 (or 3 if you count starting from today) however there is no w=
ay to extract this 2 from a lujvo meaning=C2=A0&quot;the day before yesterd=
ay&quot; (like {pruprulamdei}).</div>
<div><br></div><div>We can&#39;t use {za} either. If it&#39;s 23:00 then to=
morrow is not {baza lo djedi be li pa} because tomorrow starts in only one =
hour.</div><div><br></div><div>So here we have a different concept of split=
ting time.</div>
<div>Unlike {cacra}, {djedi}, {nanca} that split the time into intervals of=
 a fixed length (that can even overlap)</div><div>such concepts as &quot;to=
morrow&quot;, &quot;this hour&quot; split time into spliced (put in order e=
nd to end) intervals by default from midnight for &quot;day&quot;, the begi=
nning of the year (e.g. January 1) for &quot;month&quot; etc.</div>
<div><br></div><div>One workaround is {ca lo 2001moi nanca}, which is cheat=
ing since it&#39;s not stated that those one-year time intervals don&#39;t =
overlap. Other methods like cmevla for names of years described in L4B shar=
e the same problem with {cabdei}, {bavlamdei}.</div>
<div><br></div><div>What is more, I found a bunch of gismu that have this s=
plicing interval sumti type:</div><div><div>cerni1 (cerni =3D=C2=A0x1 is a =
morning of day x2 ...)</div><div>citsi</div><div>crisa</div><div>critu</div=
><div>
donri</div><div>dunra</div><div>murse</div><div>nicte</div><div>temci</div>=
<div>vanci</div><div>vensa</div></div><div>So I suggest that we use either =
a cmavo or a jvajvo-generating prefix for {djedi}, {cacra} ... to change to=
 splicing intervals when we need them.</div>
<div><br></div></div>

<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 e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

--f46d0444808d6cbc0804fff0edac--