[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lojban-beginners] Re: User interfacing in Lojban..



On 10/4/08, Killian De Volder <killian.de.volder@scarlet.be> wrote:
> Steve Sloan wrote:
> > > 2) What the computer does when the user presses it ("Apply", "Search")
> > >
> > > For 2), for instance, you can't just say "Sisku" on the button, as that
> > > (as
> > > I understand it) means "Look, a search/something searches!" which makes
> > > no
> > > sense in context.  Would the button read "ko sisku" ("Hey you,
> > > Search!")?
> >
> > I think {sisku} would be fine, as most UI labels are already ambiguous as
> > to the actor.  For example, "Get Mail" and "Print" are actions for the
> > application to perform, but "Write" and "Reply" are actions the user wants
> > to perform.  You could add {ko}/{mi}, but that would probably just make
> > things more confusing: is {mi} the user, or the application?

So, "sisku" _can_ mean "ko sisku"?

If not, then the user interface dialog could end with "doi skami [ko
sisku] [ko basti]".  The reason for not including the "doi skami" in
the button itself is so that it can reasonably apply to a list of
commands.

> How about omitting the mi / ko ? Making it unspecified, doing EXACTLY what
> you want:
> doing the same as what we read now in English, the short labels are
> ambiguous.
>
> I REALLY don't get the UI discussion issue.
> The complain is: it's not clear who the subject is ... aren't we trying to
> obtain that (ambiguously) ?
> And if you do want to show the actor, it's usually the program who is acting
> (so ko).


> A single "ok" choice je'e would be correct: "Yes I read the message you."
> But in case of a multi option je'e would be very confusing. (As Steve
> explained)