We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 62

Summary: International keyboards and CTRL
Product: SDL Reporter: Sam Lantinga <slouken>
Component: eventsAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: 2.0.0   
Hardware: All   
OS: All   

Description Sam Lantinga 2006-01-21 15:17:06 UTC 
Date: Sun, 23 Feb 2003 09:45:10 +0200 (EET)
From: M Joonas Pihlaja <jpihlaja@cc.helsinki.fi>
Subject: [SDL] International keyboards and CTRL

Hello,

How is it possible to catch CTRL modified scandinavian keys?  My
original thought was that I'd look at the modifier bits and the
unicode value.  This works for ALT modified keys[1], but on this
system (Win95, SDL1.2.5) the CTRL-&#65533;key sequence (that's CTRL-<a
with two dots on top>) gives a keysym structure with:

sym = 39 = ASCII '
unicode = 0
mod = 0x40 = LCTRL

CTRL-&#65533;(CTRL-<a with one dot on top>) on the other hand gives

sym = 91 = ASCII [
unicode = 27
mod = 0x40

My second related question is: is there any way to get the
unmodified but unicode converted character, and if so what is it?
Currently the unicode field for CTRL-<alpha> keys is in the range
1..26, but that leaves no provision for international keys.

Best Regards,

Joonas Pihlaja

[1] Only works for left-ALT modified keys, not for AltGr modified
ones, but that's another question.
Comment 1 Sam Lantinga 2006-01-21 15:18:48 UTC 
I think this will be taken care of with the keysym revamp for 1.3,
but I'll leave this open so we make sure to test it when it's in.
Comment 2 Ryan C. Gordon 2006-01-27 11:23:19 UTC 
Setting Sam as "QA Contact" on all bugs (even resolved ones) so he'll definitely be in the loop to any further discussion here about SDL.

--ryan.
Comment 3 Sam Lantinga 2009-02-16 20:41:16 UTC 
I believe this is now fixed.