You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here’s an usabilty suggestion:
If an user searches for a lujvo, but it is not in its lowest-scoring form, jbovlaste should still be able to recognize the lujvo and redirect the user to the lowest-scoring form. If there is no entry, the request fails, but if there is, the user finds the lujvo he/she/it requested. This would be helpful because it is unlikely an user does the score calculation in the head. ;-)
Currently, jbovlaste simply would not find the entry, although the user entered a perfectly valid lujvo.
Adding this feature would be also be closer to Lojban, because according to the CLL, all valid forms of a lujvo are equal.
It may be neccessary to add support for manually added redirects for the extremely rare cases a lujvo has two or more lowest-scoring forms.
The text was updated successfully, but these errors were encountered:
Here’s an usabilty suggestion:
If an user searches for a lujvo, but it is not in its lowest-scoring form, jbovlaste should still be able to recognize the lujvo and redirect the user to the lowest-scoring form. If there is no entry, the request fails, but if there is, the user finds the lujvo he/she/it requested. This would be helpful because it is unlikely an user does the score calculation in the head. ;-)
Currently, jbovlaste simply would not find the entry, although the user entered a perfectly valid lujvo.
Adding this feature would be also be closer to Lojban, because according to the CLL, all valid forms of a lujvo are equal.
It may be neccessary to add support for manually added redirects for the extremely rare cases a lujvo has two or more lowest-scoring forms.
The text was updated successfully, but these errors were encountered: