What davedes said, check the char value in keyPressed. Reason for this is on most keyboards, question mark is a shifted key -- the integer codes are for unshifted keys. You could check for KEY_SLASH and shift being down, but that is extremely not recommended, since it'll break on many non-US keyboards.

The first two, no problem. The rest ... I don't know how slick deals with the encoding involved, or if it does at all. You could try checking the char value in keyPressed the same as suggested before, perhaps print it to stdout.

It's good practice to use the unicode character escape codes rather than embedding the characters themselves in your source files; so that your source files make sense to people not using ISO 8859-1 or UTF-8.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org