Proposal: Drag-and-Drop Conversion Becomes Default

From Lojban
Revision as of 17:27, 9 September 2018 by Krtisfranks (talk | contribs) (Created page with "The idea would be to redefine: * new-"te" to mean old-"{{jvs|to'ai}}", and new-"to'ai" to mean old-"te"; * new-"ve" to mean old-"{{jvs|vo'ai}}", and new-"vo'ai" to mean old-"v...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

The idea would be to redefine:

  • new-"te" to mean old-"to'ai", and new-"to'ai" to mean old-"te";
  • new-"ve" to mean old-"vo'ai", and new-"vo'ai" to mean old-"ve";
  • new-"xe" to mean old-"xo'ai", and new-"xo'ai" to mean old-"xe".
  • "se" would be unaffected.
  • The rafsi would remain associated with the word/word form/string with which they share the first vowels, so their meanings would be redefined (but their assignment wrt word form/string would be unchanged).
    • Thus, for example: new-"-ter-" would be assigned to new-"te" and would mean old-"to'ai"/old-"-toz-" (if that rafsi is accepted); new-"-toz-" would be assigned to new-"to'ai" and would mean old-"te"/old-"-ter-". Etc.
      • If the rafsi for "te" becomes "-tel-", then exchange "-ter-" with "-tel-" throughout this example.


This would require a substantial reworking of lujvo.

It might be worth it, though, if we feel that drag-and-drop conversion is easier/requires less brain-power or is more natural. Note that rafsi ending in "l" or "r" are more coveted than those which end in "z".