No problem for me. As with every update, I was forced to manually add an entry into the layouts.conf file. There's a new "handler" line, anyway:

You are right mced, thanks a lot!

I was changing the language code to see - in the space key - which keyboard I was using: FR or FR-CH. By changing the language code I had no word prediction.

My issue was using custom layouts.conf file, without the newly added line:
I just replaced the new one with mine, thus not having an idea this line was there.
Just adding it fixed it! Thanks for pointing it out!

Probably needs to be added for external layout files too. That's why I was only missing the Bulgarian completion.

On the plus side - seems we can now use custom completion handlers

(Edited)
My "Extended English" did not work anymore. The autocompletion didn't work, nor the extra characters I added. The extra line to use Xt9inputhandler didn't do the trick at first.
But something else changed as well. I use Bitvise for SFTP to download/upload the keyboard files and xterm for the bash shell. I used to be able to paste commands into the terminal, but that doesn't work anymore.

Then I tried a second time. Uploaded the enx.conf file with the extra line to /home/nemo/Downloads, and from bash I copied the file to /usr/share/maliit/plugins/com/jolla/layouts as root. Restarted the service with killall maliit-server and it works. (First time I FTP'd the .conf file directly to /usr/share/maliit/plugins/com/jolla/layouts, probably with wrong user settings then.)

Allright, this is a silly question, I know, but I tried for some time and could not find the correct way to do this thing, so maybe soembody can help me with this.

What I'd like to accomplish, is to have a different layout based on whether the device is in portrait or landscape mode. The reason for that is that I'd like to have full set of cursor keys (up, down, left, right) in landscape mode, but just left and right in portrait.

This is what I've accomplished:

As you can see, the layout is a bit tight in the rightmost portrait view, (marked with green...) so I'd like to have just 2 buttons there.

Now, I have tried various ways to do that, but for some reason I cannot put a simple "if(...)" statement in the QML code to any place it should seemingly affect the drawing of the layout.
I suppose that is because of the way the layout is drawn, it uses some funny iterative way to do that in updateSizes() of KeyboardLayout.qml, I guess??

This is actually very good change so languages not supported by prediction won't poison the word prediction database and this also makes changing input handler much easier.

I will update RPM packages for English Dvorak, English Colemak, French-Swiss and French Bépo accordingly.

@juiceme: create two spacebar rows. One visible only when portraitMode is true and the other when portraitMode is false. I haven't tested with latest update but earlier it didn't work if visible was defined for individual keys but works for full row.

Thanks, that is something I already figured out, but where can I add the branching logic?
Now as I understand it, the QML files under the "layout" directory are data structure definitions, you cannot put if/else statements there.
There is actual running code in "KeyboardLayout.qml" for example, but it is a bit unclear to me on how that bit accesses the definition QML files that contain the actual kayboard model.

@Penguin: In some cases the prediction is not "poisoned", as with radically different languages, like English and Bulgarian, or Spanish and Hebrew, because the characters systems don't allow one showing predictions in the other.

That said, it will be a good feature the developer to be able to specify which prediction database should be used for a language. I went ahead and logged it in Together.
http://bit.ly/1m5TEfm

By the way, we have a community meeting entry about also community keyboards, see https://lists.sailfishos.org/piperma...il/004098.html

Please show up to make your voice and thoughts heard!