- Home
- Get A Printable Dictionary
- Search Best Words
- Recent Changes
- How You Can Help
- valsi - All
- valsi - Preferred Only
- natlang - All
- natlang - Preferred Only
- Languages
- XML Export
- user Listing
- Report Bugs
- Utilities
- Status
- Help
- Admin Request
- Create Account
|
Discussion of "pevna"
[parent]
[root]
Comment #4:
Re: Lojban got an issue with specifying predicate structures
|
Wuzzy (Sun May 4 18:13:46 2014)
|
Thanks, now I understand. You are talking about place names, but what has that to do with Lojban itself?
Place naming is just a convention here. Yeah, admittedly it is messy. But I don’t consider these place naming conventions (i.e. “x1”, “x2”) part of Lojban itself. So it’s not a problem with Lojban, it’s a problem with the conventions.
On the other hand, when these conventions are applied to a definition in Lojban, it gets even weirder, so that’s another problem.
Maybe these place naming conventions should be completely rethought.
A cool (partly) solution would be that jbovlaste stores information like that seperately.
|
-
Comment #5:
Re: Lojban got an issue with specifying predicate structures
|
gleki (Mon May 5 06:29:54 2014)
|
Wuzzy wrote: > Thanks, now I understand. > You are talking about place names, but what has that to do with Lojban > itself? > > Place naming is just a convention here. Yeah, admittedly it is messy. But > I don’t consider these place naming conventions (i.e. “x1”, > “x2”) part of Lojban itself. So it’s not a problem with Lojban, > it’s a problem with the conventions. > > On the other hand, when these conventions are applied to a definition in > Lojban, it gets even weirder, so that’s another problem. > > Maybe these place naming conventions should be completely rethought. > > A cool (partly) solution would be that jbovlaste stores information like > that seperately.
Even if x1, x2, x3 is a convention this convention is unable to reflect interactions of places of the same predicate.
Even if this is not the problem of Lojban it means currently Lojban is hugely underdocumented in its lexicon.
Not that there is not solution to it. I'm working on a new gismte (but it'll be ke'u in Simple English direction).
|
-
|
|
|