Revision history [back]

In 1.0.5.16 Jolla silently added the possibility for the keyboard developer to choose the prediction engine for the current language. However, adding new predictions to the user databases is useful, but sometimes can pollute the other languages with fake predictions.

In my opinion, there should be another option for choosing a user prediction database for each specific language (even the non-supported ones). This will allow separating the input and probably easy backup.

Crowd-learning prediction databases might be a good feature too, though much harder to implement.

In 1.0.5.16 Jolla silently added the possibility for the keyboard developer to choose the prediction engine for the current language. However, adding new predictions to the user databases is useful, but sometimes can pollute the other languages with fake predictions.

In my opinion, there should be another option for choosing a an user prediction database for each specific language (even the non-supported ones). This will allow separating the input and probably easy backup.

Crowd-learning prediction databases might be a good feature too, though much harder to implement.

In 1.0.5.16 Jolla silently added the possibility for the keyboard developer to choose the prediction engine for the current language. However, adding new predictions to the user databases is useful, but sometimes can pollute the other languages with fake predictions.

In my opinion, there should be another option for choosing an user prediction database for each specific language (even the non-supported ones). This will allow separating the input and probably easy backup.

Crowd-learning prediction databases might be a good feature too, though much harder to implement.