Presage-based keyboard available in Chum

Applications
#5

Re switching to Chum: if you want it now then yes. I have started discussion on whether cut our losses and drop OpenRepos distribution for the keyboard at https://github.com/sailfish-keyboard/sailfishos-presage-predictor/pull/37 . So far, no reply.

As we have dependencies in the compiled plugins (Marisa for example), uploading to OpenRepos would require uploading those as well. Which will end up as having multiple copies of the lib trees all over the place, at least my first impression of it.

After repackaging all the keyboards, databases and dictionaries to make it possible to build them at OBS and testing that it works, I think it is OK to ask users to make a step and

  • add Chum repos
  • run zypper ref && zypper up.
  • check that the packages which have to switch organization are ok and then force update them.

Now whether these packages will appear at OpenRepos depends on:

  • someone will upload them
  • OpenRepos and Chum integration will suddenly go full steam ahead

Let’s see if any of these scenarios will happen.

#6

In principle, given the needs of developers, I agree. Given what users are already faced with, I’m skeptical. I’m going to reach out to Basil to see if I can help him. As it happens, I’ve done drupal stuff in the past, so I may actually be able to support him.

In the long run, chum has to feed harbour.

2 Likes
#7

I’m trying to make a Polish keyboard but I’m stuck. I already create some corpus from two books which I’d like to play with. I have hunspell and presage rpm files. But with keyboard I’m stuck.
I followed this: https://github.com/sailfish-keyboard/sailfishos-presage-predictor/tree/master/utils/keyboard
the problem I have is that I can select the keyboard I made but when I open it example in messages I see it’s empty. in journalctl I see nothing.
So does anyone knows how to debug this? How to see what the actual problem is - empty keyboard?

#8

Can you post somewhere the keyboard RPM? Do you have some other presage-based keyboard installed (English, for example)? Does it work?

#9

@rinigus es, I have English and it works fine. Actually PL is based on the English one.
here’s the keyboard file: Upload files for free - keyboard-presage-pl_PL-1.0.0-1.noarch.rpm - ufile.io

#10

There is not available Polish corpus due to copyrights but if you want big word base you can use subcorpuses. NationalCorpusOfPolish - Computational Linguistics in Poland

#11

what copyrights?
Anyway I made corpus on my own I have the presage-lang file and hunspell file.
The only problem I have for now to get this at least somehow working is the keyboard which is not showing, there’s only empty square where the kybd should be visible.

#12

Some time ago I was thinking about making Polish keyboard for Presage. So I wrote to authors of Polish corpus and ask them if it’s available. Answer was that is not available due to copyrights of magazines, books etc. Thay send me link to subcorpuses that can be used for keyboard purposes.

#13

oh ok… well I’ve made my own now I’d like to play with it but I can’t get the keyboard working i.e. to show anything

#14

Leave for others.
turns out that I need to restart keyboard service doing:

systemctl --user restart maliit-server

After that I have keyboard with autocompletion - awsome!

1 Like
#15

I am sure that maliit restart was suggested in some README or we may even recommended reboot. Great that you’ve got it sorted.

I would like to ask you to refrain sending PMs unless there is something that involves your privacy. For example, bug reports including routes from your home, IMEI as a part of submitted logs and such. Even then, issue should be opened publicly and privacy sensitive data sent via PM. Note that when you send publicly, others may respond as well and participate in resolving the issues and save time for developers. If every user of our apps, ports will be sending all issues as PMs, developers will just not have time to develop. So, I am going to ignore your PM as it does not really contain anything that would warrant sending it privately.

#16

I wonder if they have n-grams available as those shouldn’t be hit with the same copyright issue. For example, Russian keyboard n-gram DB was based on published n-grams. Or maybe they can generate one for us using their corpus?

#17

The corpus i found -even thought creating a KB didn’t work out- was from extracting wikipedia with a script.

This might work for you.

#18

Well I’ve made a PL corpus with keyboard just as a sample, based on two books I have. Of course it’s very very small but I’m quite surprised how it works. Still the biggest problem is SFOS keyboard which is not very user friendly. Need to play with it a bit but what I have right now, for me is not bad.

#19

Anybody know how to add presage to a non-presage keyboard? I really like the “Improved English” layout, with the symbols and numbers, etc., but no presage. Also, the only option with presage is too simple - no numbers, symbols, arrows…

Screenshot_20220507_001
Screenshot_20220507_0011080×2160 276 KB

Screenshot_20220507_002
Screenshot_20220507_0021080×2160 357 KB

#20

probably by adding presage conf file like in this keyboard English US Keyboard layout with presage based text prediction | OpenRepos.net — Community Repository System

open rpm file and check keyboard files.

before that install presage

1 Like
#21

Already have Presage installed, so there is a conf file in /usr/share/maliit/plugins/com/jolla/layouts.
What I noticed is that each layout has it’s own conf file with a ‘handler’ entry. Most of them say ‘handler=Xt9InputHandler.qml’, but the Presage one says ‘handler=PresageInputHandler.qml’. If I change the handler line to ‘handler=PresageInputHandler.qml’, it causes some predictions to show up on the keyboard, where there were none before, but the predictions are frozen to the same 5 words, and they never change to show suggestions as you type…

Screenshot_20220507_003
Screenshot_20220507_0031080×2160 569 KB

Screenshot_20220507_004
Screenshot_20220507_0041080×2160 561 KB

#22

Figured it out -
It was the line in conf file that says ‘languageCode=’… In the older layouts, it said ‘languageCode=EN’, but needs to be ‘languageCode=en_US’ (or whatever)

Screenshot_20220507_005
Screenshot_20220507_0051080×2160 353 KB

1 Like
#23

And why not to use documentation: sailfishos-presage-predictor/utils/keyboard at master · sailfish-keyboard/sailfishos-presage-predictor · GitHub ?

1 Like
#24

Because reading is hard…

1 Like