Author Topic: Keyboard scheme preview - is not localized  (Read 2604 times)

Offline Stefan

  • Administrator
  • Hero Member
  • *****
  • Posts: 775
  • Karma: +6/-0
Keyboard scheme preview - is not localized
« on: October 06, 2009, 02:53:39 PM »
Tested with 723 + 726
I have english MUL windows, set to german.

"Tools > Keyboard Settings... >  [View...]"  ==> the scheme preview is not localized, see picture.

I mean Strg/Ctrl and Shift/Umschalt should be no problem,
but the scan code for the trigger key, after they modifier keys, is not expanded to correct sign.

(pseudo) Scancode '123' is on english keyboard layout '[' , but on german layout 'ß'
For "Tools > Keyboard Settings... " the scancode is correct interpreted to german glyph 'ß'.
For "Tools > Keyboard Settings... >  [View...]" it is interpreted as english '['.

« Last Edit: October 06, 2009, 03:03:53 PM by Stefan »
Stefan, HippoEDIT beta tester 
HippoEDIT - the editor programmers wants to code thyself when they are dreaming.        -Don't just edit. HippoEDIT!-

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2226
  • Karma: +37/-3
    • HippoEDIT
Re: Keyboard scheme preview - is not localized
« Reply #1 on: October 06, 2009, 11:08:18 PM »
Hi Stefan,

this is an known bug (since HE beginning :) ).
Conversion from scan code to a sign and than to HTML done via xslt (data\syntax\syntax.xslt) to have it working as local as when uploaded to server.
And of course for xslt it is a hard task to take into account localization (let say current keyboard layout), and it is hardcoded to English layout (maybe with some German extensions, do not remember already).  And because normally users assign shortcuts in English, nobody noticed, because most of the symbols match.

I can only make it working for local: do conversion manually, generate html manually, create temp file, then some when delete this temp file, because schema is loaded in external browser, it would not be possible then to preview the schema standalone and so on.
Too much effort, I would leave this like it is now. If somebody need exact values, he can check them inside of the hippoedit in keyboard options.

Best regards,