Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c00::22b as permitted sender) client-ip=2a00:1450:400c:c00::22b;
Message-ID: <5567405B.7040602@gmail.com>
Date: Thu, 28 May 2015 18:20:43 +0200
From: Ilmen <ilmen.pokebip@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bpfk-list@googlegroups.com
Subject: Re: [bpfk] Lojban word definitions style guidelines
References: <55647BCD.8060008@gmail.com> <55661E01.8030707@gmail.com> <CAO7bV+h5fk51NZotmDJeZsj9juRcu=NJ2tJdm0WjQfT7Z4pL9A@mail.gmail.com> <etPan.55672a73.63938ac7.8eb0@seas760.wireless-pennnet.upenn.edu> <CAO7bV+hzCwQ2H9DYZO2wFC9RyMj7e_4AC8z_cQ8b=pFRXkQ5Wg@mail.gmail.com>
In-Reply-To: <CAO7bV+hzCwQ2H9DYZO2wFC9RyMj7e_4AC8z_cQ8b=pFRXkQ5Wg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------070802030506040909060403"
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
Sender: bpfk-list@googlegroups.com
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -

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


On 28/05/2015 16:56, Gleki Arxokuna wrote:
>
>>     Also etymology somewhat contradicts my proposal:
>>     https://github.com/lojban/jbovlaste/issues/131where we have
>>     etymology only in Lojban whereas for the other languages they can
>>     be generated by third party software like those that produce
>>     printable dictionaries.
>
>     Uh, what are they generating from, then?
>
> As I understood in this proposal for every language there is a 
> separate entry with etymology. All such entries can be autogenerated 
> from Lojban one.

I'm not certain whether Naours suggest there should be one etymology 
field for each definition.

I can imagine a case where two experimental cmavo or gismu would have 
two distinct and incompatible definitions, along with two unrelated 
source/etymology, although that seems to be a pretty uncommon case.

On the other hand, copying manually the etymology field to each 
definition would be a boring task, if not a chore.

Another option would be to have definitions grouped by proposed meaning 
(each of those meaning groups would probably be restricted to one 
definition entry per language), and have one etymology field attached to 
each proposed meaning group, so as to avoid redundancy.

mi'e la .ilmen. mu'o

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

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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type=
">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    <br>
    <div class=3D"moz-cite-prefix">On 28/05/2015 16:56, Gleki Arxokuna
      wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CAO7bV+hzCwQ2H9DYZO2wFC9RyMj7e_4AC8z_cQ8b=3DpFRXkQ5Wg@mail.gmai=
l.com"
      type=3D"cite">
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div style=3D"word-wrap:break-word">
                <div><span class=3D"">
                    <div>
                      <blockquote type=3D"cite"
style=3D"color:rgb(0,0,0);font-family:Helvetica,Arial;font-size:13px;font-s=
tyle:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;li=
ne-height:normal;text-align:start;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"><span>
                          <div>
                            <div>
                              <div dir=3D"ltr">
                                <div>Also etymology somewhat contradicts
                                  my proposal:=C2=A0<a moz-do-not-send=3D"t=
rue"
href=3D"https://github.com/lojban/jbovlaste/issues/131" target=3D"_blank">h=
ttps://github.com/lojban/jbovlaste/issues/131</a><span>=C2=A0</span>where
                                  we have etymology only in Lojban
                                  whereas for the other languages they
                                  can be generated by third party
                                  software like those that produce
                                  printable dictionaries.</div>
                              </div>
                            </div>
                          </div>
                        </span></blockquote>
                    </div>
                  </span></div>
                <p>Uh, what are they generating from, then?</p>
              </div>
            </blockquote>
            <div>As I understood in this proposal for every language
              there is a separate entry with etymology. All such entries
              can be autogenerated from Lojban one. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I'm not certain whether Naours suggest there should be one etymology
    field for each definition.<br>
    <br>
    I can imagine a case where two experimental cmavo or gismu would
    have two distinct and incompatible definitions, along with two
    unrelated source/etymology, although that seems to be a pretty
    uncommon case.<br>
    <br>
    On the other hand, copying manually the etymology field to each
    definition would be a boring task, if not a chore.<br>
    <br>
    Another option would be to have definitions grouped by proposed
    meaning (each of those meaning groups would probably be restricted
    to one definition entry per language), and have one etymology field
    attached to each proposed meaning group, so as to avoid redundancy.<br>
    <br>
    mi'e la .ilmen. mu'o<br>
    <br>
  </body>
</html>

<p></p>

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

--------------070802030506040909060403--