Re: [g-a-devel]Re: gok 0.9.3 released - keyboards now i18n-ready

[David Bolter <david bolter utoronto ca>]

Danilo,

I'll try to respond to some of your points tomorrow when I have time to 
address them properly. I think you have uncovered some important issues 
and it will be invaluable to have your help addressing them.

Perhaps I will make a few quick comments for now:

Danilo Šegan wrote:
> (Please CC me on responses, since I'm not on a11y list)
>
> Bill Haneman <Bill Haneman Sun COM> writes:
>
> > Please see the special README-TRANSLATORS file also.  If you are
> > planning to use GOK in a non-latin locale, please contact
> > gnome-accessibility-devel gnome org, since we'd like to make sure GOK is
> > working well in your locale.
>
>
> I've just installed and tried GOK 0.9.3, and I'm using it in Serbian
> locale (cyrillic) -- it's available from
> http://srpski.org/locale/sr_CS (not yet in GNU libc, but I hope it
> will get there soon).
>
> What you're mostly interested in is probably the fact that the
> onscreen keyboard seems to function all right for input of Serbian
> cyrillic characters, if I've got a correct XKB map in place.
>
> (Apart from getting one crash, but didn't run it from inside GDB that
> time, and cannot reproduce it now:
>
> Gdk-ERROR **: The program 'gok' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
>   (Details: serial 6947 error_code 8 request_code 42 minor_code 0)
> )
>
> Also, I experienced a bunch of other problems.
>
> Apparently, not all strings are extracted for translation from
> main.kbd.in (eg. nothing shows up for "Compose"). Also, even though
> "Menus" is translated and later merged into sr/main.kbd correctly, it
> didn't show up either. Actually, the entire first screen of GOK was
> untranslated for me.
>
> Next, when I switched from one mode to other (eg. from main screen to
> GOK, and back), window size was automatically reduced, and performing
> these steps several times led to getting smaller and smaller
> fonts (I cannot reproduce this either). 
>
> When I tried to exit from GOK section using "Quit GOK", button "Really
> Quit!" for confirming exit didn't do anything (except for
> flashing). This one I can reproduce steadily.

This is a known issue.  It is related to a recent change we made 
regarding generated the generated xml for the keyboards.
http://bugzilla.gnome.org/show_bug.cgi?id=126813

> Also, I noticed that GOK actually produces the keycodes, and not the
> keysymbols corresponding to characters. This means that I must have
> appropriate Serbian map so that characters would correspond with
> reality (and the one I used [and developed] will be included with
> XFree86 4.4, which is not yet released).
>
> Also, if there are several groups loaded, and I switch to other
> keyboard group, glyph images on the keyboard don't correspond at all
> to the characters that are output (eg. if I switch to en_US XKB map
> in XFree86 4.3, and use Serbian locale for GOK, it outputs latin "B"
> instead of cyrillic "Б" which is showed on screen).
>
> I've expected that pressing "Shift" images with mouse in "Compose"
> mode would also show the 2nd level of keyboard, but that didn't
> happen -- if I press the real Shift key on keyboard, it happens all
> right. Ditto for ISO_Level3_Shift.
>
> I think the correct approach would be to read the data about groups
> and levels from X server, or at least to always output what is shown
> on screen (i.e., output a keysym, and not a keycode). Using
> translations of "level0|..." strings seems inappropriate, especially
> so in cases like that of Serbian where there are several keyboard
> maps with slight differences, so it would not work correctly with
> some of them.
>
>
> Okay, I didn't have accessibility features turned on (GOK warned me
> about it at start up), so that may be causing some of my problems
> (though I believe that's only the reason why my "Menus", "Toolbars"
> and "UI Grab" buttons are disabled, though I may be mistaken).

That is correct. Those keys are only enabled if accessibility is turned 
on and the forground application is accessible (e.g. gedit).  These keys 
allow branching to keyboards that are reproductions of the forground 
application's GUI (e.g. gedit's menus).

That's all I can manage for now.  Talk to you soon,

David

> If you wish, I may file any or all of these as bugs, and I can
> probably provide more info if you tell me what to look at. Of course,
> I don't have much clue about any of the stuff GOK needs to 
> perform, so be sure to brief me on exactly what you need done, and
> what info you may require.
>
> Cheers,
> Danilo
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel