The missing stylus keyboard is one of the major bugs on that bug list. (It's in the first post - take a look at it before asking about something that doesn't work right and your question might be answered before being asked.) I've done some debugging here, and it seems AbiWord has to manually call a GTK+ Input Method and Hildon call on an input method context to pop up the stylus keyboard when you tap within the document area. That code is there, however, the call is failing because the pointer to the gtk im context is either null or invalid, I can't remember which. I'm not entirely sure why that is the case - my next debugging step there is to make sure we actually have that im context pointer on a desktop version (because if it's bad there too, then if I can't fix it, another dev can do so more easily), and if it's only bad on Maemo, I need to trace the lifetime of that pointer and see where it's getting accidentally destroyed. This is actually not the hardest one to do, since it happens all the time and it's very simple to test, and I have an N800 which I can test with and which incentivizes my fix (I can't use AbiWord on there without my BT keyboard until it's fixed!) . I'm guessing, too, that once that gets fixed, the full-screen keyboard bug might be fixed, since those are both input-related, and if we truly have a bogus input method context, then there's no guarantee anything works right in the weird-input world outside of a hardware us-101 keyboard. We'll see - I really would like to fix this one!

(PS: If _anyone_ can get the small stylus keyboard (not the full-screen thumb keyboard) up in this version, please tell me how! That has the potential to lead right to the bug!)

There's another bug like this that probably affects a lot, and that's the one where it asserts all the time in debug mode. If it's asserting in debug mode, that might mean things are silently failing in regular mode, and it's asserting in normally (and cross-platform) good code, which means somewhere along the calling line something is getting botched, and somewhere that has an #ifdef for maemo.

Maybe you can buy the time of a skilled hildon hacker (I may be a hacker, and I may be somewhat skilled, but without hildon experience and I'm learning GTK+ right now) who lurks here on the boards - best way to do so would probably be to add as a comment to the bug and announce here how much you bounty it, and the conditions for the bounty to be fulfilled (presumably bug fixed and fix reviewed by Abi devs and checked in).