https://bugzilla.wikimedia.org/show_bug.cgi?id=28900
Siddhartha Ghai <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Siddhartha Ghai <[email protected]> 2012-04-15 12:15:21 UTC --- (In reply to comment #3) > We have added support for on-screen keyboards for InScript key mappings. It is > currently triggered using a CGI parameter. I've set up a simple test case at > https://translatewiki.net/wiki/User:Siebrand/testosk. Feedback is welcome! > Feedback: I don't know tamil but I think that the keyboard should show the latin alphabet that's on the user's physical keyboard along with the tamil output so that the user can get acquainted with the rules easily and type from the keyboard instead of having to press the buttons on the onscreen keyboard. Also, clicking on shift changes the keys width (since the letters change) and hence the keyboard moves a bit on the screen. It should remain fixed. We also probably want it to remain at a fixed position on the screen instead of moving whenever we go to a different input field. This could probably be done by keeping it in a jquery UI dialog which is draggable so that the user can position it where he wants. But the dialog should open by default at a fixed place on the screen (e.g the top-left corner) no matter which input field is clicked on. > The on-screen keyboards for phonetic mappings are much more difficult from a > design and usability perspective. We need many months more before we will have > a solution for that. What we would ideally need is a program to dynamically make the keyboard from the input rules of each language method (so that we don't have to worry about modifying onscreenkeyboard code every time the rules are modified). This should be easy to do for inscript schemes, a little difficult for phonetic (transliteration) inputs. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
