Re: [lazarus] utf-8/unicode and keyboard input

2007-10-14 Thread Graeme Geldenhuys
On 12/10/2007, Andreas Gick <[EMAIL PROTECTED]> wrote: > > I tried commenting out "if (Ord(AText[1]) > 31) and (Ord(AText[1]) < 127) > then" and the corresponding "begin end;" structure, but it didn't seem to > change anything. As the code comment states, that procedure still needs work. The bes

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-12 Thread Marc Santhoff
Am Freitag, den 12.10.2007, 14:02 +0200 schrieb Andreas Gick: > Well the most obvious place, where the keycode could vanish is the following > procedure: > > procedure TfpgEdit.HandleKeyChar(var AText: string; > var shiftstate: TShiftState; var consumed: boolean); > var > s: string; > prev

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-12 Thread Andreas Gick
Am Mittwoch 03 Oktober 2007 03:09:34 schrieb Marc Santhoff: > Am Dienstag, den 02.10.2007, 18:50 +0200 schrieb Andreas Gick: > > Thanks for the quick answers > > > > Well there is a similar function in the source of fpgui that I included > > as attachment (at around line 414), and I'm not sure,

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-04 Thread Graeme Geldenhuys
On 04/10/2007, Felipe Monteiro de Carvalho <[EMAIL PROTECTED]> wrote: > > The interface code is responsible for getting the events (thougth > whatever mechanism the toolkit provides) and send those events to LCL. > > LCL will not try to bypass the toolkit and use its own ways to get > keyboard or a

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-04 Thread Felipe Monteiro de Carvalho
On 10/3/07, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote: > Using fpGUI as a widget set in Lazarus. How would this affect things? > Does the underlying toolkit pass keyboard input to LCL or does it go > from LCL to the underlying toolkit? The interface code is responsible for getting the events (

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-04 Thread Marc Santhoff
Am Mittwoch, den 03.10.2007, 12:11 +0200 schrieb Graeme Geldenhuys: > Using fpGUI as a widget set in Lazarus. How would this affect things? > Does the underlying toolkit pass keyboard input to LCL or does it go > from LCL to the underlying toolkit? I have no idea about that. Use the source, Luke

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-03 Thread Graeme Geldenhuys
On 03/10/2007, Marc Santhoff <[EMAIL PROTECTED]> wrote: > > I'd try by using an xterm and setting locale to "de_DE.ISO8859-15" or > whatever it's named on your System. After that you can start a test > program from that xterm. > > Last time when I was localizing a program I made a new user having $

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-03 Thread Marc Santhoff
Am Mittwoch, den 03.10.2007, 08:52 +0200 schrieb Graeme Geldenhuys: > How do I enter a 'ö' character when I use a Programmer Dvorak keyboard > layout and my Linux LANG environment variable is set to > "en_ZA.UTF-8"?? Do I need to change my keyboard to a German (or any > other foreign language) la

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-02 Thread Graeme Geldenhuys
On 03/10/2007, Marc Santhoff <[EMAIL PROTECTED]> wrote: > So if you compile the code with debug defined you will most likely see > the event getting translated by > > function TfpgApplicationImpl.KeySymToKeycode(KeySym: TKeySym): Word; That's correct. Enabling the DEBUG define in the top of the u

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-02 Thread Marc Santhoff
Am Dienstag, den 02.10.2007, 18:50 +0200 schrieb Andreas Gick: > Thanks for the quick answers > > Well there is a similar function in the source of fpgui that I included as > attachment (at around line 414), and I'm not sure, why it only works with > ASCII characters. > > But maybe I also

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-01 Thread Marc Santhoff
Am Montag, den 01.10.2007, 13:16 +0200 schrieb Marc Santhoff: > ks := XStringToKeysym(pchar(key)); > kc := XKeySymToKeycode( display, ks ); Sorry, but this is not really correct, you more likely want to do it the other way round: XKeycodeToKeysym(...) seems to be more approp

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-01 Thread Marc Santhoff
Am Montag, den 01.10.2007, 12:35 +0200 schrieb Andreas Gick: > Hi everybody, > > as I want to help out with internationalization of the fpGUI widget set at > least for the X-Window system, I need some information on how the keysyms of > the X-Window can be translated into characters. > > For e

Re: [lazarus] utf-8/unicode and keyboard input

2007-10-01 Thread ik
Hi, I'm using my memory here, so I might remember it wrongly... There is a difference between a scan code, and the actual char. to "know" the actual char, you need to know what is the language layout that you are at. There is an X "debug" program to know what scan code was pressed and it's value

[lazarus] utf-8/unicode and keyboard input

2007-10-01 Thread Andreas Gick
Hi everybody, as I want to help out with internationalization of the fpGUI widget set at least for the X-Window system, I need some information on how the keysyms of the X-Window can be translated into characters. For example pressing the german umlaut "ö" on my german keyboard results accord