Received-SPF: pass (google.com: domain of seladwa@gmx.de designates 212.227.17.21 as permitted sender) client-ip=212.227.17.21;
Message-ID: <55663BFF.3020909@gmx.de>
Date: Wed, 27 May 2015 23:49:51 +0200
From: selpa'i <seladwa@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bpfk-list@googlegroups.com
Subject: Re: [bpfk] Re: Lojban word definitions style guidelines
References: <55647BCD.8060008@gmail.com> <55661E01.8030707@gmail.com> <55662400.6030807@gmail.com> <etPan.55662e80.29fc58cb.8eb0@seas760.wireless-pennnet.upenn.edu>
In-Reply-To: <etPan.55662e80.29fc58cb.8eb0@seas760.wireless-pennnet.upenn.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: -

la durka cu cusku di'e
> As for sumti slots in lujvo definitions, I favor the hybrid system
> (x1=g1=s2 is a thing with ...). It's visually noisy, but it manages to
> (1) number the places without obliging the reader to count and (2) show
> the "etymology" of each place, where that is relevant. I consider (1)
> more important -- perhaps the notes are a better place to say which
> terjvo came from which veljvo.

I would think so. I prefer the simplest method: just x_n. Not everyone 
cares about the origin of the lujvo places, and all those letters 
clutter up the definition and make it look more like math than anything.

What I thought could work is to have an extra field apart from the 
general notes field that can be used to give information about place 
structure patterns ("families") and other place structure background. 
Maybe a good dictionary frontend would allow the user to choose if they 
want this field to be visible (like a show/hide button). Much like 
etymology, it's not necessary to know about it, but it can be of value 
to the interested.

I do think the definitions should be as easy to read as possible, and 
readable by a layperson.

I talked to some people a while ago, and they told me the definition 
style scared them off, because it reminded them of math. It wouldn't 
hurt Lojban to cater to a wider audience (as crazy as that may sound!) 
by making sure that any person with any background can access it. When 
giving lessons to non-math/non-programming people I sometimes use 
unnumbered blanks written by underscores, because the concept of filling 
in the blanks is easy to grasp and less intimidating than "filling 
argument places" for certain people. It looks like this:

dunda: ___ gives ___ to ___

I'm not saying this should replace the x1,x2,x3 style, but I think it is 
a good alternative that could be implemented in some potential 
dictionary interface as an additional option. Everyone should be able to 
feel comfortable reading the dictionary.

mi'e la selpa'i 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.