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

[lojban] Re: The Usability Project





On Tuesday, August 20, 2013 8:31:35 PM UTC+4, Dmitriy Remselgin wrote:


On Tuesday, August 20, 2013 9:35:34 PM UTC+6, la arxokuna wrote:


Yes,  that's why we imported the content of all old pages into our new wiki. http://mw.lojban.org It uses the same engine as Wikipedia.
So everything that is possible for Wikipedia is possible for Jupiter si Lojbanic Mediawiki (LMW, mw.lojban.org).


Well done! But wiki is good for reference materials. A newbie will be overwhelmed if he or she tries to use wiki for learning.


Parses - yep, translates - nope.

Well, Lojban has it's syntax detached from it's semantics. It's a great step towards machine translation. If you can go further in the direction of  semantical translation I can only welcome it.

Though camxes is a great step in the right direction, cause it uses visualization.
 
So... I assume you can help, right?

Surely. BTW, I'm a programmer. But obviously I cannot do all this work by myself. It is not an issue of some minor fixes or improvements such as fixing the jbovlaste web-pages - it is an issue of a global change of the way the information is presented and processed.

At the moment I'm working on new textbooks. One of them is an updated Lojban for Beginners. Another one would be a fork of it in a new direction. Yet another one would be a short addendum to it written for mathematicians and logicians. Another textbook will be a fork of Wave lessons. Another tutorial will use some methods of teaching natlangs. And the last project in this series is writing a bidirectional converter of our reference grammar - CLL (docbook format<=>mediawiki format). 
Working on CLL in docbook format is actually the most important work. We need a fully documented language. So take a look at it. https://github.com/dag/cll




The way information about lojban is presented on its official resources may be appropriate for a small group of men working together, but it is not if we take into account newbies spread all over the world and even active "lojban developers". The current lojban project interface (i.e. its site, textbooks, media, reference etc.) looks like "Hey, guy, there's some awesome stuff inside, but you must read this big grammar with plain black text on the background, crunch a heap of mailing lists, and then you'll certainly appreciate its awesomeness".

Even after reading those mailing lists you'll have to somehow combine them with CLL in your head. In order to make that simpler we first need to finish docbook-CLL. Currently no one is working on it. That's the problem. After finishing it we will be able to quickly update it to match the current state of affairs.

 
Lojban is really awesome, and it must look beautiful and attractive for everyone.

We can add interactive elements, browser applications, games, consistent learning programs for different kinds of users, we can form translator teams, add special features for "lojban developers" and even for BFPK if it will countinue its work... Also we have to remove outdated resources from main site and store them as history in the wiki, for example.

In LMW (mw.lojban.org) all pages from the old wiki are prefixed with "Old Pages: ". So they are in another namespace. Can there be better solutions?

I have a lot of ideas, and later I will make a detailed roadmap about this update.

Sure. Don't forget to include docbook-CLL in it. Without it all the work will stall.
 
I hope most of lojbanists will support it, but still it is a team work, and any help will be appreciated, especially from those who have been with lojban for a long time.

--
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/groups/opt_out.