Is there any L10n feature planned or some interface where I can build my own?
Since our project is directed mainly to German users, they want to have their quotation marks on Shift-2, not on Shift-Ä (2 keys to the right of L), as printed on their keys. Any way I can switch or at least detect the locale settings?
Localisation
Moderators: CEGUI MVP, CEGUI Team
- Blakharaz
- Not too shy to talk
- Posts: 31
- Joined: Wed Jan 12, 2005 12:06
- Location: Potsdam, Germany
- Contact:
Localisation
Coder in the Pantheon Team - creators of "Rastullahs Lockenpracht" (http://www.rastullahs-lockenpracht.de/)
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Localisation
Hi,
I'm in England, and we have our quotation marks on Shift-2 also
The system does not deal with this side of things, as they're better dealt with somewhere else. Keyboard character inputs are literally injected into the GUI system via the System::injectCharacter method, which takes a Unicode UTF32 code point. Using this approach, everybody is free to use any source of inputs they wish (ogre, direct input, win32, SDL, etc) - so the localisation issues you mention become a job for the input library rather than the GUI system itself.
I presume you're using the Ogre/CEGui demos as a guide for implementing your own stuff, in these demos all inputs are coming from the Ogre inputs system - which obviously does no translation of key strokes for localisation
Sinbad will tell you that the inputs system within Ogre was never intended as a solution to such problems, but more of a means to support the samples that they provide. I can only suggest that you seek out an alternative source of keyboard character inputs.
I'm in England, and we have our quotation marks on Shift-2 also

The system does not deal with this side of things, as they're better dealt with somewhere else. Keyboard character inputs are literally injected into the GUI system via the System::injectCharacter method, which takes a Unicode UTF32 code point. Using this approach, everybody is free to use any source of inputs they wish (ogre, direct input, win32, SDL, etc) - so the localisation issues you mention become a job for the input library rather than the GUI system itself.
I presume you're using the Ogre/CEGui demos as a guide for implementing your own stuff, in these demos all inputs are coming from the Ogre inputs system - which obviously does no translation of key strokes for localisation

Return to “Bug Reports, Suggestions, Feature Requests”
Who is online
Users browsing this forum: No registered users and 2 guests