Re: latin2 keyboard in LyX 1.1.6fix1

[Robin Turner]

On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:


 There is a known problem with turkish locales, which is the 'i' is not
 the lower case variant of 'I'. This breaks the parsing of layout
 files (where keywords are case-insensitive). Try to set the
 environment variable LC_COLLATE to C.

Hey, it works!  Thanks.


Robin

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

 Robin == Robin Turner [EMAIL PROTECTED] writes:

Robin On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:
  There is a known problem with turkish locales, which is the 'i' is
 not the lower case variant of 'I'. This breaks the parsing of
 layout files (where keywords are case-insensitive). Try to set the
 environment variable LC_COLLATE to C.

Robin Hey, it works! Thanks.

Of course, it would be better if somebody took the time to really fix
the bug... Not difficult, really.

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Robin Turner]

On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:


 There is a known problem with turkish locales, which is the 'i' is not
 the lower case variant of 'I'. This breaks the parsing of layout
 files (where keywords are case-insensitive). Try to set the
 environment variable LC_COLLATE to C.

Hey, it works!  Thanks.


Robin

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

 Robin == Robin Turner [EMAIL PROTECTED] writes:

Robin On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:
  There is a known problem with turkish locales, which is the 'i' is
 not the lower case variant of 'I'. This breaks the parsing of
 layout files (where keywords are case-insensitive). Try to set the
 environment variable LC_COLLATE to C.

Robin Hey, it works! Thanks.

Of course, it would be better if somebody took the time to really fix
the bug... Not difficult, really.

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Robin Turner]

On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:

>
> There is a known problem with turkish locales, which is the 'i' is not
> the lower case variant of 'I'. This breaks the parsing of layout
> files (where keywords are case-insensitive). Try to set the
> environment variable LC_COLLATE to "C".

Hey, it works!  Thanks.


Robin

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

> "Robin" == Robin Turner <[EMAIL PROTECTED]> writes:

Robin> On Monday 14 May 2001 11:22, Jean-Marc Lasgouttes wrote:
>>  There is a known problem with turkish locales, which is the 'i' is
>> not the lower case variant of 'I'. This breaks the parsing of
>> layout files (where keywords are case-insensitive). Try to set the
>> environment variable LC_COLLATE to "C".

Robin> Hey, it works! Thanks.

Of course, it would be better if somebody took the time to really fix
the bug... Not difficult, really.

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

 Robin == Robin Turner [EMAIL PROTECTED] writes:

Robin Sounds a bit like my Turkish problem, which I've been messing
Robin around with for a while now. If I install Mandrake 7.2 with
Robin English as the default language, I can't get Turkish
Robin characters, except by using the Turkish keymap in the lyx
Robin directory, which is totally weird - has loads of things in the
Robin wrong place and still misses some characters (the Turkish
Robin X-fonts _are_ installed, BTW!). If I install with Turkish as
Robin the default language, older versions of LyX crash on trying to
Robin read the Article class, while 1.1.6 won't give any menu bars.
Robin Klyx also segfaults as soon as I try to open a document. Looks
Robin like some fundamental problem with libc.

There is a known problem with turkish locales, which is the 'i' is not
the lower case variant of 'I'. This breaks the parsing of layout
files (where keywords are case-insensitive). Try to set the
environment variable LC_COLLATE to C.

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

 Robin == Robin Turner [EMAIL PROTECTED] writes:

Robin Sounds a bit like my Turkish problem, which I've been messing
Robin around with for a while now. If I install Mandrake 7.2 with
Robin English as the default language, I can't get Turkish
Robin characters, except by using the Turkish keymap in the lyx
Robin directory, which is totally weird - has loads of things in the
Robin wrong place and still misses some characters (the Turkish
Robin X-fonts _are_ installed, BTW!). If I install with Turkish as
Robin the default language, older versions of LyX crash on trying to
Robin read the Article class, while 1.1.6 won't give any menu bars.
Robin Klyx also segfaults as soon as I try to open a document. Looks
Robin like some fundamental problem with libc.

There is a known problem with turkish locales, which is the 'i' is not
the lower case variant of 'I'. This breaks the parsing of layout
files (where keywords are case-insensitive). Try to set the
environment variable LC_COLLATE to C.

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Jean-Marc Lasgouttes]

> "Robin" == Robin Turner <[EMAIL PROTECTED]> writes:

Robin> Sounds a bit like my Turkish problem, which I've been messing
Robin> around with for a while now. If I install Mandrake 7.2 with
Robin> English as the default language, I can't get Turkish
Robin> characters, except by using the Turkish keymap in the lyx
Robin> directory, which is totally weird - has loads of things in the
Robin> wrong place and still misses some characters (the Turkish
Robin> X-fonts _are_ installed, BTW!). If I install with Turkish as
Robin> the default language, older versions of LyX crash on trying to
Robin> read the Article class, while 1.1.6 won't give any menu bars.
Robin> Klyx also segfaults as soon as I try to open a document. Looks
Robin> like some fundamental problem with libc.

There is a known problem with turkish locales, which is the 'i' is not
the lower case variant of 'I'. This breaks the parsing of layout
files (where keywords are case-insensitive). Try to set the
environment variable LC_COLLATE to "C".

JMarc

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

I am sorry, I forgot to send this to the list as well.

Matej

 Date: Fri, 11 May 2001 00:39:30 -0400
 From: Matej Cepl matej
 Subject: Re: latin2 keyboard in LyX 1.1.6fix1
 To: Roman Maurer [EMAIL PROTECTED]
 
 On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
  Matej Cepl wrote:
   
   Then tell me, pray, how to get working Czech keyboard in LyX with well
   behaving X with localized keyboard? I have never managed to do that :-(
  
  Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
  recompile it.  It should work from then on.
 
 Well, now I have spent two hours to create my debugging  version of lyx
 (non-stripped binary has 36M! -- boy, we have grown up :-), so that I
 could create you this beautiful backtrace of core dump. What do you
 think about that?
 
 Thanks for effort, anyway!
 
 Matej
 
 Starting program: /usr/src/redhat/BUILD/lyx-1.1.6fix1/src/./lyx 
 [New Thread 1024 (LWP 1064)]
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 1024 (LWP 1064)]
 0x0 in ?? ()
 Current language:  auto; currently c
 (gdb) bt
 #0  0x0 in ?? ()
 #1  0x83679aa in __user_type_info::dyncast (this=0x84b7f0c, boff=0, 
 target=@0x84b7f0c, objptr=0xbfffe824, subtype=@0x84ad940, subptr=0xbfffe824)
 #2  0x8367347 in __dynamic_cast_2 (from=0x836d370 stringbuf type_info function,
 to=0x836d370 stringbuf type_info function, boff=0, address=0xbfffe824,
 sub=0x80520b4 streambuf type_info function, subptr=0xbfffe824)
 #3  0x8362260 in lyx::tempName (dir=@0xbfffea10, mask=@0xbfffea20)
 at /usr/include/g++-3/sstream:65
 #4  0x834fc91 in CreateTmpDir (tempdir=@0xbfffea10, mask=@0xbfffea20)
 at filetools.C:445
 #5  0x8350831 in CreateLyXTmpDir (deflt=@0x84b4e34)
 at /usr/include/g++-3/std/bastring.h:183
 #6  0x815607b in LyX::init (this=0xb7c0, argv=0xb884, gui=true)
 at /usr/include/g++-3/std/bastring.h:171
 #7  0x814e50c in LyX::LyX (this=0x0, argc=0xb820, argv=0xb884)
 at ../src/lyx_main.C:104
 #8  0x81b815c in main (argc=1, argv=0xb884) at ../src/main.C:40
 #9  0x40149a7c in __libc_start_main (main=0x81b7fd0 main, argc=1, 
 ubp_av=0xb884, init=0x80501fc _init, fini=0x83fb50c _fini, 
 rtld_fini=0x4000d684 _dl_fini, stack_end=0xb87c)
 at ../sysdeps/generic/libc-start.c:111
 (gdb) 

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Fri, May 11, 2001 at 08:22:29AM +0200, Roman Maurer wrote:
 
 What does lyx -dbg key say?

Well, actually nothing -- it cores dump before, it manages to say 
anything. :-)

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

I am sorry, I forgot to send this to the list as well.

Matej

 Date: Fri, 11 May 2001 00:39:30 -0400
 From: Matej Cepl matej
 Subject: Re: latin2 keyboard in LyX 1.1.6fix1
 To: Roman Maurer [EMAIL PROTECTED]
 
 On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
  Matej Cepl wrote:
   
   Then tell me, pray, how to get working Czech keyboard in LyX with well
   behaving X with localized keyboard? I have never managed to do that :-(
  
  Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
  recompile it.  It should work from then on.
 
 Well, now I have spent two hours to create my debugging  version of lyx
 (non-stripped binary has 36M! -- boy, we have grown up :-), so that I
 could create you this beautiful backtrace of core dump. What do you
 think about that?
 
 Thanks for effort, anyway!
 
 Matej
 
 Starting program: /usr/src/redhat/BUILD/lyx-1.1.6fix1/src/./lyx 
 [New Thread 1024 (LWP 1064)]
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 1024 (LWP 1064)]
 0x0 in ?? ()
 Current language:  auto; currently c
 (gdb) bt
 #0  0x0 in ?? ()
 #1  0x83679aa in __user_type_info::dyncast (this=0x84b7f0c, boff=0, 
 target=@0x84b7f0c, objptr=0xbfffe824, subtype=@0x84ad940, subptr=0xbfffe824)
 #2  0x8367347 in __dynamic_cast_2 (from=0x836d370 stringbuf type_info function,
 to=0x836d370 stringbuf type_info function, boff=0, address=0xbfffe824,
 sub=0x80520b4 streambuf type_info function, subptr=0xbfffe824)
 #3  0x8362260 in lyx::tempName (dir=@0xbfffea10, mask=@0xbfffea20)
 at /usr/include/g++-3/sstream:65
 #4  0x834fc91 in CreateTmpDir (tempdir=@0xbfffea10, mask=@0xbfffea20)
 at filetools.C:445
 #5  0x8350831 in CreateLyXTmpDir (deflt=@0x84b4e34)
 at /usr/include/g++-3/std/bastring.h:183
 #6  0x815607b in LyX::init (this=0xb7c0, argv=0xb884, gui=true)
 at /usr/include/g++-3/std/bastring.h:171
 #7  0x814e50c in LyX::LyX (this=0x0, argc=0xb820, argv=0xb884)
 at ../src/lyx_main.C:104
 #8  0x81b815c in main (argc=1, argv=0xb884) at ../src/main.C:40
 #9  0x40149a7c in __libc_start_main (main=0x81b7fd0 main, argc=1, 
 ubp_av=0xb884, init=0x80501fc _init, fini=0x83fb50c _fini, 
 rtld_fini=0x4000d684 _dl_fini, stack_end=0xb87c)
 at ../sysdeps/generic/libc-start.c:111
 (gdb) 

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Fri, May 11, 2001 at 08:22:29AM +0200, Roman Maurer wrote:
 
 What does lyx -dbg key say?

Well, actually nothing -- it cores dump before, it manages to say 
anything. :-)

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

I am sorry, I forgot to send this to the list as well.

Matej

> Date: Fri, 11 May 2001 00:39:30 -0400
> From: Matej Cepl 
> Subject: Re: latin2 keyboard in LyX 1.1.6fix1
> To: Roman Maurer <[EMAIL PROTECTED]>
> 
> On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
> > Matej Cepl wrote:
> > > 
> > > Then tell me, pray, how to get working Czech keyboard in LyX with well
> > > behaving X with localized keyboard? I have never managed to do that :-(
> > 
> > Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
> > recompile it.  It should work from then on.
> 
> Well, now I have spent two hours to create my debugging  version of lyx
> (non-stripped binary has 36M! -- boy, we have grown up :-), so that I
> could create you this beautiful backtrace of core dump. What do you
> think about that?
> 
> Thanks for effort, anyway!
> 
> Matej
> 
> Starting program: /usr/src/redhat/BUILD/lyx-1.1.6fix1/src/./lyx 
> [New Thread 1024 (LWP 1064)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 1064)]
> 0x0 in ?? ()
> Current language:  auto; currently c
> (gdb) bt
> #0  0x0 in ?? ()
> #1  0x83679aa in __user_type_info::dyncast (this=0x84b7f0c, boff=0, 
> target=@0x84b7f0c, objptr=0xbfffe824, subtype=@0x84ad940, subptr=0xbfffe824)
> #2  0x8367347 in __dynamic_cast_2 (from=0x836d370 ,
> to=0x836d370 , boff=0, address=0xbfffe824,
> sub=0x80520b4 , subptr=0xbfffe824)
> #3  0x8362260 in lyx::tempName (dir=@0xbfffea10, mask=@0xbfffea20)
> at /usr/include/g++-3/sstream:65
> #4  0x834fc91 in CreateTmpDir (tempdir=@0xbfffea10, mask=@0xbfffea20)
> at filetools.C:445
> #5  0x8350831 in CreateLyXTmpDir (deflt=@0x84b4e34)
> at /usr/include/g++-3/std/bastring.h:183
> #6  0x815607b in LyX::init (this=0xb7c0, argv=0xb884, gui=true)
> at /usr/include/g++-3/std/bastring.h:171
> #7  0x814e50c in LyX::LyX (this=0x0, argc=0xb820, argv=0xb884)
> at ../src/lyx_main.C:104
> #8  0x81b815c in main (argc=1, argv=0xb884) at ../src/main.C:40
> #9  0x40149a7c in __libc_start_main (main=0x81b7fd0 , argc=1, 
> ubp_av=0xb884, init=0x80501fc <_init>, fini=0x83fb50c <_fini>, 
> rtld_fini=0x4000d684 <_dl_fini>, stack_end=0xb87c)
> at ../sysdeps/generic/libc-start.c:111
> (gdb) 

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Fri, May 11, 2001 at 08:22:29AM +0200, Roman Maurer wrote:
> 
> What does "lyx -dbg key" say?

Well, actually nothing -- it cores dump before, it manages to say 
anything. :-)

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
 Matej Cepl wrote:
  
  Then tell me, pray, how to get working Czech keyboard in LyX with well
  behaving X with localized keyboard? I have never managed to do that :-(
 
 Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
 recompile it.  It should work from then on.

Do I have to wait till I recompile with -g option on (cca 2 hours) or 
are you able to recognize what's on from this bactkrace?

matej $ gdb lyx 
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are welcome to change it and/or distribute copies of it under certain 
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for 
details.
This GDB was configured as i386-redhat-linux...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/lyx 
[New Thread 1024 (LWP 9469)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 9469)]
0x0 in ?? ()
(gdb) bt
#0  0x0 in ?? ()
#1  0x835608a in __rtti_user ()
#2  0x8355a27 in __dynamic_cast ()
#3  0x8350bd0 in fl_set_button ()
#4  0x833edc8 in fl_set_button ()
#5  0x833f943 in fl_set_button ()
#6  0x8150adc in fl_set_button ()
#7  0x81492c5 in fl_set_button ()
#8  0x81b1db6 in fl_set_button ()
#9  0x40149a7c in __libc_start_main (main=0x81b1c20 fl_set_button+1440496, 
argc=1, ubp_av=0xb8c4, init=0x80501d8 _init, fini=0x83e3a6c _fini, 
rtld_fini=0x4000d684 _dl_fini, stack_end=0xb8bc)
at ../sysdeps/generic/libc-start.c:111
(gdb) The program is running.  Exit anyway? (y or n) y
matej $ 

However, thanks for try.

Matej   

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
  Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
  recompile it.  It should work from then on.
 
 Do I have to wait till I recompile with -g option on (cca 2 hours) or
 are you able to recognize what's on from this bactkrace?

Oops, sorry!  :---(  It worked for me and apparently it worked for
Sasa too.

What system are you using and what is the contents of your
.lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
and report what you do and what is says, so that I can try to reproduce
this.

However, I don't know anything about the design of LyX - it just
made me sad because I couldn't write our alphabet.  Hope that
LyX developers are reading this and are wiling to help.

I tested that patch on two systems: one with RedHat Linux 6.1 with
egcs-2.91.66 and glibc 2.1.2 and the other with SuSE Linux 7.0 and
default libraries (don't know them right now).

 Starting program: /usr/bin/lyx
 [New Thread 1024 (LWP 9469)]
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 1024 (LWP 9469)]
 [...]
 However, thanks for try.

You're welcome.  I apology for any inconvenience.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Thu, May 10, 2001 at 11:19:29PM +0200, Roman Maurer wrote:
 Matej Cepl wrote:
 
 What system are you using and what is the contents of your
 .lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
 and report what you do and what is says, so that I can try to reproduce
 this.

RedHat 7.0 (rpm -q glibc gives glibc-2.2-5 and rpm -q gcc gives 
gcc-2.96-54; both default from the distribution) with XFree 4.0.1.
Preferences files is attached. Report from non-stripped version of
backtrack core was send to the  list.
 
 However, I don't know anything about the design of LyX - it just
 made me sad because I couldn't write our alphabet.  Hope that
 LyX developers are reading this and are wiling to help.

I hope so too. :-)

So, what to do now (except from recompiling without 
your patch to get clean version again -- I have
screwed up the previous clean version; shame on me)?

Thanks

Matej
 preferences.gz

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
 Matej Cepl wrote:
  
  Then tell me, pray, how to get working Czech keyboard in LyX with well
  behaving X with localized keyboard? I have never managed to do that :-(
 
 Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
 recompile it.  It should work from then on.

Do I have to wait till I recompile with -g option on (cca 2 hours) or 
are you able to recognize what's on from this bactkrace?

matej $ gdb lyx 
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are welcome to change it and/or distribute copies of it under certain 
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for 
details.
This GDB was configured as i386-redhat-linux...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/lyx 
[New Thread 1024 (LWP 9469)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 9469)]
0x0 in ?? ()
(gdb) bt
#0  0x0 in ?? ()
#1  0x835608a in __rtti_user ()
#2  0x8355a27 in __dynamic_cast ()
#3  0x8350bd0 in fl_set_button ()
#4  0x833edc8 in fl_set_button ()
#5  0x833f943 in fl_set_button ()
#6  0x8150adc in fl_set_button ()
#7  0x81492c5 in fl_set_button ()
#8  0x81b1db6 in fl_set_button ()
#9  0x40149a7c in __libc_start_main (main=0x81b1c20 fl_set_button+1440496, 
argc=1, ubp_av=0xb8c4, init=0x80501d8 _init, fini=0x83e3a6c _fini, 
rtld_fini=0x4000d684 _dl_fini, stack_end=0xb8bc)
at ../sysdeps/generic/libc-start.c:111
(gdb) The program is running.  Exit anyway? (y or n) y
matej $ 

However, thanks for try.

Matej   

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
  Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
  recompile it.  It should work from then on.
 
 Do I have to wait till I recompile with -g option on (cca 2 hours) or
 are you able to recognize what's on from this bactkrace?

Oops, sorry!  :---(  It worked for me and apparently it worked for
Sasa too.

What system are you using and what is the contents of your
.lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
and report what you do and what is says, so that I can try to reproduce
this.

However, I don't know anything about the design of LyX - it just
made me sad because I couldn't write our alphabet.  Hope that
LyX developers are reading this and are wiling to help.

I tested that patch on two systems: one with RedHat Linux 6.1 with
egcs-2.91.66 and glibc 2.1.2 and the other with SuSE Linux 7.0 and
default libraries (don't know them right now).

 Starting program: /usr/bin/lyx
 [New Thread 1024 (LWP 9469)]
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 1024 (LWP 9469)]
 [...]
 However, thanks for try.

You're welcome.  I apology for any inconvenience.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Thu, May 10, 2001 at 11:19:29PM +0200, Roman Maurer wrote:
 Matej Cepl wrote:
 
 What system are you using and what is the contents of your
 .lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
 and report what you do and what is says, so that I can try to reproduce
 this.

RedHat 7.0 (rpm -q glibc gives glibc-2.2-5 and rpm -q gcc gives 
gcc-2.96-54; both default from the distribution) with XFree 4.0.1.
Preferences files is attached. Report from non-stripped version of
backtrack core was send to the  list.
 
 However, I don't know anything about the design of LyX - it just
 made me sad because I couldn't write our alphabet.  Hope that
 LyX developers are reading this and are wiling to help.

I hope so too. :-)

So, what to do now (except from recompiling without 
your patch to get clean version again -- I have
screwed up the previous clean version; shame on me)?

Thanks

Matej
 preferences.gz

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Wed, May 09, 2001 at 08:31:36AM +0200, Roman Maurer wrote:
> Matej Cepl wrote:
> > 
> > Then tell me, pray, how to get working Czech keyboard in LyX with well
> > behaving X with localized keyboard? I have never managed to do that :-(
> 
> Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
> recompile it.  It should work from then on.

Do I have to wait till I recompile with -g option on (cca 2 hours) or 
are you able to recognize what's on from this bactkrace?

matej $ gdb lyx 
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
This GDB was configured as "i386-redhat-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/lyx 
[New Thread 1024 (LWP 9469)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 9469)]
0x0 in ?? ()
(gdb) bt
#0  0x0 in ?? ()
#1  0x835608a in __rtti_user ()
#2  0x8355a27 in __dynamic_cast ()
#3  0x8350bd0 in fl_set_button ()
#4  0x833edc8 in fl_set_button ()
#5  0x833f943 in fl_set_button ()
#6  0x8150adc in fl_set_button ()
#7  0x81492c5 in fl_set_button ()
#8  0x81b1db6 in fl_set_button ()
#9  0x40149a7c in __libc_start_main (main=0x81b1c20 , 
argc=1, ubp_av=0xb8c4, init=0x80501d8 <_init>, fini=0x83e3a6c <_fini>, 
rtld_fini=0x4000d684 <_dl_fini>, stack_end=0xb8bc)
at ../sysdeps/generic/libc-start.c:111
(gdb) The program is running.  Exit anyway? (y or n) y
matej $ 

However, thanks for try.

Matej   

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
> 
> > Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
> > recompile it.  It should work from then on.
> 
> Do I have to wait till I recompile with -g option on (cca 2 hours) or
> are you able to recognize what's on from this bactkrace?

Oops, sorry!  :---(  It worked for me and apparently it worked for
Sasa too.

What system are you using and what is the contents of your
.lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
and report what you do and what is says, so that I can try to reproduce
this.

However, I don't know anything about the design of LyX - it just
made me sad because I couldn't write our alphabet.  Hope that
LyX developers are reading this and are wiling to help.

I tested that patch on two systems: one with RedHat Linux 6.1 with
egcs-2.91.66 and glibc 2.1.2 and the other with SuSE Linux 7.0 and
default libraries (don't know them right now).

> Starting program: /usr/bin/lyx
> [New Thread 1024 (LWP 9469)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 9469)]
> [...]
> However, thanks for try.

You're welcome.  I apology for any inconvenience.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Thu, May 10, 2001 at 11:19:29PM +0200, Roman Maurer wrote:
> Matej Cepl wrote:
> 
> What system are you using and what is the contents of your
> .lyxrc/preferences?  Please run LyX in debug mode (e. g. lyx -dbg key)
> and report what you do and what is says, so that I can try to reproduce
> this.

RedHat 7.0 (rpm -q glibc gives glibc-2.2-5 and rpm -q gcc gives 
gcc-2.96-54; both default from the distribution) with XFree 4.0.1.
Preferences files is attached. Report from non-stripped version of
backtrack core was send to the  list.
 
> However, I don't know anything about the design of LyX - it just
> made me sad because I couldn't write our alphabet.  Hope that
> LyX developers are reading this and are wiling to help.

I hope so too. :-)

So, what to do now (except from recompiling without 
your patch to get clean version again -- I have
screwed up the previous clean version; shame on me)?

Thanks

Matej
 preferences.gz

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
 Then tell me, pray, how to get working Czech keyboard in LyX with well
 behaving X with localized keyboard? I have never managed to do that :-(

Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
recompile it.  It should work from then on.
-- 
Regards,
  Roman

--- src/kbsequence.C.orig   Sun Dec 17 07:09:34 2000
+++ src/kbsequence.CWed May  9 00:53:49 2001
@@ -261,6 +261,9 @@
 char kb_sequence::getiso() const
 {
int const c = getsym();
+
+   if (c = 0x1a1  c = 0x1ff)  // ISO Latin 2 keysym
+   return static_castchar(c % 256);

if (c  0xff)
return '\0';

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
 Then tell me, pray, how to get working Czech keyboard in LyX with well
 behaving X with localized keyboard? I have never managed to do that :-(

Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
recompile it.  It should work from then on.
-- 
Regards,
  Roman

--- src/kbsequence.C.orig   Sun Dec 17 07:09:34 2000
+++ src/kbsequence.CWed May  9 00:53:49 2001
@@ -261,6 +261,9 @@
 char kb_sequence::getiso() const
 {
int const c = getsym();
+
+   if (c = 0x1a1  c = 0x1ff)  // ISO Latin 2 keysym
+   return static_castchar(c % 256);

if (c  0xff)
return '\0';

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
> 
> Then tell me, pray, how to get working Czech keyboard in LyX with well
> behaving X with localized keyboard? I have never managed to do that :-(

Patch the file src/kbsequence.C for LyX 1.1.6fix1 with this patch and
recompile it.  It should work from then on.
-- 
Regards,
  Roman

--- src/kbsequence.C.orig   Sun Dec 17 07:09:34 2000
+++ src/kbsequence.CWed May  9 00:53:49 2001
@@ -261,6 +261,9 @@
 char kb_sequence::getiso() const
 {
int const c = getsym();
+
+   if (c >= 0x1a1 && c <= 0x1ff)  // ISO Latin 2 keysym
+   return static_cast(c % 256);

if (c > 0xff)
return '\0';

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Lars Gullik Bjnnes wrote:
 
 Roman Maurer [EMAIL PROTECTED] writes:
 
 | Roman Maurer wrote:
 | 
 |  I'd like to extend LyX with support for Latin-2 keyboards, I just
 |  don't know if I'll know enough to do this.  Could someone please
 |  tell me where to start (I downloaded the sources and I know some C++)?
 
 AFAIK all this is font problems.

It's not exactly the font problem - it's the fact that keycodes
from Latin-2 X keyboard don't really match ISO codes for Latin-2
characters.  In Latin-1 there's no such problem.

What we would need is a mapping function that would translate
X keycodes to ISO Latin 2 character codes, like this one:

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...

The value from the "keycode" column is fetched via getsym() and
the "ISO Latin 2 code" value should be returned by kb_sequence::getiso().
For Latin-1, this table will be like that:

keycodeISO Latin 2 letter  ISO Latin 2 code
232egrave  232
185onesuperior 185
190threequarters   190
...

STL's std::map could do the trick for all ISO encodings.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl [EMAIL PROTECTED] writes:

| On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjønnes wrote:
|  | 
|  | No, the problem is that LyX ignores any X keyboard at all and relies 
|  | solely on its own power (which is The Bad Thing, IMHO).
|  
|  explain.
| 
| Well, I am not a programmer, but IMVHO programms should do only one 
| thing and do it well. Therefore, I do not like programms which try to 
| do things which are clearly not appropriate for them -- especially 
| localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
| should just get the information about the character have ben typed in 
| from X and all .kmap files should go straight into the waste bin.

Then don't use them. I never do... for any for the latinX chars I need
to write.

_but_ if you wan't some of the special chars you need a font that
contain the correct glyphs. also we will not support any of this
_well_ before each code have one glyph. (this means unicode)

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Tue, May 08, 2001 at 11:43:04AM +0200, Lars Gullik Bjnnes wrote:
 Then don't use them. I never do... for any for the latinX chars I need
 to write.
 
 _but_ if you wan't some of the special chars you need a font that
 contain the correct glyphs. also we will not support any of this
 _well_ before each code have one glyph. (this means unicode)

Then tell me, pray, how to get working Czech keyboard in LyX with well 
behaving X with localized keyboard? I have never managed to do that :-(

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Lars Gullik Bjnnes wrote:
 
 Roman Maurer [EMAIL PROTECTED] writes:
 
 | Roman Maurer wrote:
 | 
 |  I'd like to extend LyX with support for Latin-2 keyboards, I just
 |  don't know if I'll know enough to do this.  Could someone please
 |  tell me where to start (I downloaded the sources and I know some C++)?
 
 AFAIK all this is font problems.

It's not exactly the font problem - it's the fact that keycodes
from Latin-2 X keyboard don't really match ISO codes for Latin-2
characters.  In Latin-1 there's no such problem.

What we would need is a mapping function that would translate
X keycodes to ISO Latin 2 character codes, like this one:

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...

The value from the "keycode" column is fetched via getsym() and
the "ISO Latin 2 code" value should be returned by kb_sequence::getiso().
For Latin-1, this table will be like that:

keycodeISO Latin 2 letter  ISO Latin 2 code
232egrave  232
185onesuperior 185
190threequarters   190
...

STL's std::map could do the trick for all ISO encodings.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl [EMAIL PROTECTED] writes:

| On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjønnes wrote:
|  | 
|  | No, the problem is that LyX ignores any X keyboard at all and relies 
|  | solely on its own power (which is The Bad Thing, IMHO).
|  
|  explain.
| 
| Well, I am not a programmer, but IMVHO programms should do only one 
| thing and do it well. Therefore, I do not like programms which try to 
| do things which are clearly not appropriate for them -- especially 
| localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
| should just get the information about the character have ben typed in 
| from X and all .kmap files should go straight into the waste bin.

Then don't use them. I never do... for any for the latinX chars I need
to write.

_but_ if you wan't some of the special chars you need a font that
contain the correct glyphs. also we will not support any of this
_well_ before each code have one glyph. (this means unicode)

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Tue, May 08, 2001 at 11:43:04AM +0200, Lars Gullik Bjnnes wrote:
 Then don't use them. I never do... for any for the latinX chars I need
 to write.
 
 _but_ if you wan't some of the special chars you need a font that
 contain the correct glyphs. also we will not support any of this
 _well_ before each code have one glyph. (this means unicode)

Then tell me, pray, how to get working Czech keyboard in LyX with well 
behaving X with localized keyboard? I have never managed to do that :-(

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Lars Gullik Bjnnes wrote:
> 
> Roman Maurer <[EMAIL PROTECTED]> writes:
> 
> | Roman Maurer wrote:
> | >
> | > I'd like to extend LyX with support for Latin-2 keyboards, I just
> | > don't know if I'll know enough to do this.  Could someone please
> | > tell me where to start (I downloaded the sources and I know some C++)?
> 
> AFAIK all this is font problems.

It's not exactly the font problem - it's the fact that keycodes
from Latin-2 X keyboard don't really match ISO codes for Latin-2
characters.  In Latin-1 there's no such problem.

What we would need is a mapping function that would translate
X keycodes to ISO Latin 2 character codes, like this one:

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...

The value from the "keycode" column is fetched via getsym() and
the "ISO Latin 2 code" value should be returned by kb_sequence::getiso().
For Latin-1, this table will be like that:

keycodeISO Latin 2 letter  ISO Latin 2 code
232egrave  232
185onesuperior 185
190threequarters   190
...

STL's std::map could do the trick for all ISO encodings.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl <[EMAIL PROTECTED]> writes:

| On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjønnes wrote:
| > | 
| > | No, the problem is that LyX ignores any X keyboard at all and relies 
| > | solely on its own power (which is The Bad Thing, IMHO).
| > 
| > explain.
| 
| Well, I am not a programmer, but IMVHO programms should do only one 
| thing and do it well. Therefore, I do not like programms which try to 
| do things which are clearly not appropriate for them -- especially 
| localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
| should just get the information about the character have ben typed in 
| from X and all .kmap files should go straight into the waste bin.

Then don't use them. I never do... for any for the latinX chars I need
to write.

_but_ if you wan't some of the special chars you need a font that
contain the correct glyphs. also we will not support any of this
_well_ before each code have one glyph. (this means unicode)

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Tue, May 08, 2001 at 11:43:04AM +0200, Lars Gullik Bjnnes wrote:
> Then don't use them. I never do... for any for the latinX chars I need
> to write.
> 
> _but_ if you wan't some of the special chars you need a font that
> contain the correct glyphs. also we will not support any of this
> _well_ before each code have one glyph. (this means unicode)

Then tell me, pray, how to get working Czech keyboard in LyX with well 
behaving X with localized keyboard? I have never managed to do that :-(

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
 However, I feel that there is really something screwed up in the
 KDE keyboard management (actually, it is the only thing which
 seemes to be actually worse than it was in KDE 1.1, where kikbd was
 the Great Thing).

I don't know what keyboard are you using, but the new Slovenian
X-keyboard is definitely the right one, e. g. it sends Latin-2
characters "ccaron", "scaron" and "zcaron" instead of "egrave",
"onesuperior" and "threequarters", respectively.

The problem with LyX is probable that it currently only supports
Latin-1 keyboard input.  This is logical explanation why LyX
doesn't work with the new keyboard even if it used to work with
the old (Latin-1) one.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
 
 The problem with LyX is probable that it currently only supports
 Latin-1 keyboard input.  This is logical explanation why LyX
 doesn't work with the new keyboard even if it used to work with
 the old (Latin-1) one.

No, the problem is that LyX ignores any X keyboard at all and relies 
solely on its own power (which is The Bad Thing, IMHO).

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl [EMAIL PROTECTED] writes:

| On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
|  
|  The problem with LyX is probable that it currently only supports
|  Latin-1 keyboard input.  This is logical explanation why LyX
|  doesn't work with the new keyboard even if it used to work with
|  the old (Latin-1) one.
| 
| No, the problem is that LyX ignores any X keyboard at all and relies 
| solely on its own power (which is The Bad Thing, IMHO).

explain.

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sun, 6 May 2001, Matej Cepl wrote:

 For me it was enough just to switch to English keyboard while using
 LyX and then to the Czech one when switched to some other application.

Thank you very much for the tip - it works!

Until now, I was using LyX under KDE with my Xmodmap (on one user
aacount), but I didn't have Croatian chars outside of LyX.

Now, I just can switch between the two keyboard layouts (US  Slovene
since there is no Croatia in KDE 2.0.x), although it would be normal to
have LyX  other KDE apps work under the same i.e. Slovene or Croatian
keyboard layout.

Any tip how to configure some shortcut key for switching between the
keyboard layouts?

One more question:

Where I can modify  English keyboard for KDE in order to define Win Menu
key as 'backslash' and to define Letf  Right Win keys to work as
Mode_switch in order to add some definitions for Sanskrit diacritics?

Before I just modified Xmodmap, but now I am not sure what to do in KDE
2.0.x (in KDe 1.1.x it was easy with the *.kimap files).

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Sasa Janiska wrote:
 
 On Sun, 6 May 2001, Matej Cepl wrote:
 
  For me it was enough just to switch to English keyboard while using
  LyX and then to the Czech one when switched to some other application.
 
 Thank you very much for the tip - it works!

But this is not how it's supposed to be - Latin-2 keyboard should
suffice to enter Latin-2 characters, it's not so good if you always
have to switch back and forth between different keyboards.

I'd like to extend LyX with support for Latin-2 keyboards, I just
don't know if I'll know enough to do this.  Could someone please
tell me where to start (I downloaded the sources and I know some C++)?

 Any tip how to configure some shortcut key for switching between the
 keyboard layouts?

In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Roman Maurer wrote:
 
 I'd like to extend LyX with support for Latin-2 keyboards, I just
 don't know if I'll know enough to do this.  Could someone please
 tell me where to start (I downloaded the sources and I know some C++)?

I managed to convince LyX to display "" when I pressed the button
with "ccaron".  I put this stupid code into kbsequence.C, function
kb_sequence::getiso() after "... c = getsym()":

if (c == 488)  // 488 is X keycode for key ccaron
  return 232;  // this is ISO Latin 2 code for letter ccaron

Are there any plans to extend LyX keyboard input with a lookup
table or something like that?  For ISO Latin 1, lookup will luckily
be 1-1, but for ISO Latin 2, it will be more complicated, e. g.

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...
etc.

This would improve usefulnes of LyX for non-Latin-1-keyboard users.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Roman Maurer [EMAIL PROTECTED] writes:

| Roman Maurer wrote:
|  
|  I'd like to extend LyX with support for Latin-2 keyboards, I just
|  don't know if I'll know enough to do this.  Could someone please
|  tell me where to start (I downloaded the sources and I know some C++)?

AFAIK all this is font problems.
 
-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 05:54:00PM +0200, Roman Maurer wrote:

 In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.

One of the reasons, why I switched off the KDE keyboard support, that 
they have now as the default switching shortcut, Ctrl-Alt-K and you 
cannot changed to Alt+Shift nor Boht-Shifts.

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjnnes wrote:
 | 
 | No, the problem is that LyX ignores any X keyboard at all and relies 
 | solely on its own power (which is The Bad Thing, IMHO).
 
 explain.

Well, I am not a programmer, but IMVHO programms should do only one 
thing and do it well. Therefore, I do not like programms which try to 
do things which are clearly not appropriate for them -- especially 
localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
should just get the information about the character have ben typed in 
from X and all .kmap files should go straight into the waste bin. I 
understand, that LyX's own support for i18n of keyboard is historical 
residuum from times when there were no good localizations, but it seems 
to me, that now bare X is able to support nearly any language 
imagianble and if not (I ahve no idea, whether there is an support of 
Arabic), it would be better to create partciular modules for X not for 
LyX.

Better GUII would be another nice result of it (how is the localization 
of the keyboard done in M$-Windows of LyX?).

Matj

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Mon, 7 May 2001, Roman Maurer wrote:

 I managed to convince LyX to display "" when I pressed the button
 with "ccaron".  I put this stupid code into kbsequence.C, function
 kb_sequence::getiso() after "... c = getsym()":


Hey, that's great!

Thank you for taking time to improve LyX.

 This would improve usefulnes of LyX for non-Latin-1-keyboard users.

And I believe it could also bring many new users to LyX.

LyX simply has some 'smell' as a killer application for Linux, it just
needs a little bit ...

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
 
 However, I feel that there is really something screwed up in the
 KDE keyboard management (actually, it is the only thing which
 seemes to be actually worse than it was in KDE 1.1, where kikbd was
 the Great Thing).

I don't know what keyboard are you using, but the new Slovenian
X-keyboard is definitely the right one, e. g. it sends Latin-2
characters "ccaron", "scaron" and "zcaron" instead of "egrave",
"onesuperior" and "threequarters", respectively.

The problem with LyX is probable that it currently only supports
Latin-1 keyboard input.  This is logical explanation why LyX
doesn't work with the new keyboard even if it used to work with
the old (Latin-1) one.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
 
 The problem with LyX is probable that it currently only supports
 Latin-1 keyboard input.  This is logical explanation why LyX
 doesn't work with the new keyboard even if it used to work with
 the old (Latin-1) one.

No, the problem is that LyX ignores any X keyboard at all and relies 
solely on its own power (which is The Bad Thing, IMHO).

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl [EMAIL PROTECTED] writes:

| On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
|  
|  The problem with LyX is probable that it currently only supports
|  Latin-1 keyboard input.  This is logical explanation why LyX
|  doesn't work with the new keyboard even if it used to work with
|  the old (Latin-1) one.
| 
| No, the problem is that LyX ignores any X keyboard at all and relies 
| solely on its own power (which is The Bad Thing, IMHO).

explain.

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sun, 6 May 2001, Matej Cepl wrote:

 For me it was enough just to switch to English keyboard while using
 LyX and then to the Czech one when switched to some other application.

Thank you very much for the tip - it works!

Until now, I was using LyX under KDE with my Xmodmap (on one user
aacount), but I didn't have Croatian chars outside of LyX.

Now, I just can switch between the two keyboard layouts (US  Slovene
since there is no Croatia in KDE 2.0.x), although it would be normal to
have LyX  other KDE apps work under the same i.e. Slovene or Croatian
keyboard layout.

Any tip how to configure some shortcut key for switching between the
keyboard layouts?

One more question:

Where I can modify  English keyboard for KDE in order to define Win Menu
key as 'backslash' and to define Letf  Right Win keys to work as
Mode_switch in order to add some definitions for Sanskrit diacritics?

Before I just modified Xmodmap, but now I am not sure what to do in KDE
2.0.x (in KDe 1.1.x it was easy with the *.kimap files).

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Sasa Janiska wrote:
 
 On Sun, 6 May 2001, Matej Cepl wrote:
 
  For me it was enough just to switch to English keyboard while using
  LyX and then to the Czech one when switched to some other application.
 
 Thank you very much for the tip - it works!

But this is not how it's supposed to be - Latin-2 keyboard should
suffice to enter Latin-2 characters, it's not so good if you always
have to switch back and forth between different keyboards.

I'd like to extend LyX with support for Latin-2 keyboards, I just
don't know if I'll know enough to do this.  Could someone please
tell me where to start (I downloaded the sources and I know some C++)?

 Any tip how to configure some shortcut key for switching between the
 keyboard layouts?

In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Roman Maurer wrote:
 
 I'd like to extend LyX with support for Latin-2 keyboards, I just
 don't know if I'll know enough to do this.  Could someone please
 tell me where to start (I downloaded the sources and I know some C++)?

I managed to convince LyX to display "" when I pressed the button
with "ccaron".  I put this stupid code into kbsequence.C, function
kb_sequence::getiso() after "... c = getsym()":

if (c == 488)  // 488 is X keycode for key ccaron
  return 232;  // this is ISO Latin 2 code for letter ccaron

Are there any plans to extend LyX keyboard input with a lookup
table or something like that?  For ISO Latin 1, lookup will luckily
be 1-1, but for ISO Latin 2, it will be more complicated, e. g.

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...
etc.

This would improve usefulnes of LyX for non-Latin-1-keyboard users.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Roman Maurer [EMAIL PROTECTED] writes:

| Roman Maurer wrote:
|  
|  I'd like to extend LyX with support for Latin-2 keyboards, I just
|  don't know if I'll know enough to do this.  Could someone please
|  tell me where to start (I downloaded the sources and I know some C++)?

AFAIK all this is font problems.
 
-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 05:54:00PM +0200, Roman Maurer wrote:

 In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.

One of the reasons, why I switched off the KDE keyboard support, that 
they have now as the default switching shortcut, Ctrl-Alt-K and you 
cannot changed to Alt+Shift nor Boht-Shifts.

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjnnes wrote:
 | 
 | No, the problem is that LyX ignores any X keyboard at all and relies 
 | solely on its own power (which is The Bad Thing, IMHO).
 
 explain.

Well, I am not a programmer, but IMVHO programms should do only one 
thing and do it well. Therefore, I do not like programms which try to 
do things which are clearly not appropriate for them -- especially 
localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
should just get the information about the character have ben typed in 
from X and all .kmap files should go straight into the waste bin. I 
understand, that LyX's own support for i18n of keyboard is historical 
residuum from times when there were no good localizations, but it seems 
to me, that now bare X is able to support nearly any language 
imagianble and if not (I ahve no idea, whether there is an support of 
Arabic), it would be better to create partciular modules for X not for 
LyX.

Better GUII would be another nice result of it (how is the localization 
of the keyboard done in M$-Windows of LyX?).

Matj

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Mon, 7 May 2001, Roman Maurer wrote:

 I managed to convince LyX to display "" when I pressed the button
 with "ccaron".  I put this stupid code into kbsequence.C, function
 kb_sequence::getiso() after "... c = getsym()":


Hey, that's great!

Thank you for taking time to improve LyX.

 This would improve usefulnes of LyX for non-Latin-1-keyboard users.

And I believe it could also bring many new users to LyX.

LyX simply has some 'smell' as a killer application for Linux, it just
needs a little bit ...

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Matej Cepl wrote:
> 
> However, I feel that there is really something screwed up in the
> KDE keyboard management (actually, it is the only thing which
> seemes to be actually worse than it was in KDE 1.1, where kikbd was
> the Great Thing).

I don't know what keyboard are you using, but the new Slovenian
X-keyboard is definitely the right one, e. g. it sends Latin-2
characters "ccaron", "scaron" and "zcaron" instead of "egrave",
"onesuperior" and "threequarters", respectively.

The problem with LyX is probable that it currently only supports
Latin-1 keyboard input.  This is logical explanation why LyX
doesn't work with the new keyboard even if it used to work with
the old (Latin-1) one.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
> 
> The problem with LyX is probable that it currently only supports
> Latin-1 keyboard input.  This is logical explanation why LyX
> doesn't work with the new keyboard even if it used to work with
> the old (Latin-1) one.

No, the problem is that LyX ignores any X keyboard at all and relies 
solely on its own power (which is The Bad Thing, IMHO).

Matej

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Matej Cepl <[EMAIL PROTECTED]> writes:

| On Mon, May 07, 2001 at 09:18:04AM +0200, Roman Maurer wrote:
| > 
| > The problem with LyX is probable that it currently only supports
| > Latin-1 keyboard input.  This is logical explanation why LyX
| > doesn't work with the new keyboard even if it used to work with
| > the old (Latin-1) one.
| 
| No, the problem is that LyX ignores any X keyboard at all and relies 
| solely on its own power (which is The Bad Thing, IMHO).

explain.

-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sun, 6 May 2001, Matej Cepl wrote:

> For me it was enough just to switch to English keyboard while using
> LyX and then to the Czech one when switched to some other application.

Thank you very much for the tip - it works!

Until now, I was using LyX under KDE with my Xmodmap (on one user
aacount), but I didn't have Croatian chars outside of LyX.

Now, I just can switch between the two keyboard layouts (US & Slovene
since there is no Croatia in KDE 2.0.x), although it would be normal to
have LyX & other KDE apps work under the same i.e. Slovene or Croatian
keyboard layout.

Any tip how to configure some shortcut key for switching between the
keyboard layouts?

One more question:

Where I can modify  English keyboard for KDE in order to define Win Menu
key as 'backslash' and to define Letf & Right Win keys to work as
Mode_switch in order to add some definitions for Sanskrit diacritics?

Before I just modified Xmodmap, but now I am not sure what to do in KDE
2.0.x (in KDe 1.1.x it was easy with the *.kimap files).

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Sasa Janiska wrote:
> 
> On Sun, 6 May 2001, Matej Cepl wrote:
> 
> > For me it was enough just to switch to English keyboard while using
> > LyX and then to the Czech one when switched to some other application.
> 
> Thank you very much for the tip - it works!

But this is not how it's supposed to be - Latin-2 keyboard should
suffice to enter Latin-2 characters, it's not so good if you always
have to switch back and forth between different keyboards.

I'd like to extend LyX with support for Latin-2 keyboards, I just
don't know if I'll know enough to do this.  Could someone please
tell me where to start (I downloaded the sources and I know some C++)?

> Any tip how to configure some shortcut key for switching between the
> keyboard layouts?

In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Roman Maurer wrote:
> 
> I'd like to extend LyX with support for Latin-2 keyboards, I just
> don't know if I'll know enough to do this.  Could someone please
> tell me where to start (I downloaded the sources and I know some C++)?

I managed to convince LyX to display "" when I pressed the button
with "ccaron".  I put this stupid code into kbsequence.C, function
kb_sequence::getiso() after "... c = getsym()":

if (c == 488)  // 488 is X keycode for key ccaron
  return 232;  // this is ISO Latin 2 code for letter ccaron

Are there any plans to extend LyX keyboard input with a lookup
table or something like that?  For ISO Latin 1, lookup will luckily
be 1-1, but for ISO Latin 2, it will be more complicated, e. g.

keycodeISO Latin 2 letter  ISO Latin 2 code
488ccaron  232
441scaron  185
446zcaron  190
...
etc.

This would improve usefulnes of LyX for non-Latin-1-keyboard users.
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Lars Gullik Bjønnes]

Roman Maurer <[EMAIL PROTECTED]> writes:

| Roman Maurer wrote:
| > 
| > I'd like to extend LyX with support for Latin-2 keyboards, I just
| > don't know if I'll know enough to do this.  Could someone please
| > tell me where to start (I downloaded the sources and I know some C++)?

AFAIK all this is font problems.
 
-- 
Lgb

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 05:54:00PM +0200, Roman Maurer wrote:

> In KDE 1.1.2 it was Ctrl+Alt or Shift+Alt or something like that.

One of the reasons, why I switched off the KDE keyboard support, that 
they have now as the default switching shortcut, Ctrl-Alt-K and you 
cannot changed to Alt+Shift nor Boht-Shifts.

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Mon, May 07, 2001 at 04:00:32PM +0200, Lars Gullik Bjnnes wrote:
> | 
> | No, the problem is that LyX ignores any X keyboard at all and relies 
> | solely on its own power (which is The Bad Thing, IMHO).
> 
> explain.

Well, I am not a programmer, but IMVHO programms should do only one 
thing and do it well. Therefore, I do not like programms which try to 
do things which are clearly not appropriate for them -- especially 
localization of keyboard (e.g. Emacs and LyX). It seems to me, that LyX 
should just get the information about the character have ben typed in 
from X and all .kmap files should go straight into the waste bin. I 
understand, that LyX's own support for i18n of keyboard is historical 
residuum from times when there were no good localizations, but it seems 
to me, that now bare X is able to support nearly any language 
imagianble and if not (I ahve no idea, whether there is an support of 
Arabic), it would be better to create partciular modules for X not for 
LyX.

Better GUII would be another nice result of it (how is the localization 
of the keyboard done in M$-Windows of LyX?).

Matj

-- 
Matej Cepl, [EMAIL PROTECTED]
138 Highland Ave. #10
Somerville, Ma 02143
(617) 623-1488

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Mon, 7 May 2001, Roman Maurer wrote:

> I managed to convince LyX to display "" when I pressed the button
> with "ccaron".  I put this stupid code into kbsequence.C, function
> kb_sequence::getiso() after "... c = getsym()":
>

Hey, that's great!

Thank you for taking time to improve LyX.

> This would improve usefulnes of LyX for non-Latin-1-keyboard users.

And I believe it could also bring many new users to LyX.

LyX simply has some 'smell' as a killer application for Linux, it just
needs a little bit ...

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sat, 5 May 2001, Matej Cepl wrote:

 I am a Czech user of the Lyx and I am very happy with that. Actually,
 setting of the keyboard is rather tricky. You have to switch OFF your
 main X keyboard (or change to English) and then set ON the Slovenian
 (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
 course, that you should have set characters to Latin-2.


Do you use LyX under KDE?

The problem is that finally under KDe 2.0.x I have Croatian characters
(latin2) under KDE in all applications - except in LyX.

If I want to have latin-2 characters in LyX, I have to sacrifice them in
all other applications under KDE - it is not really cosmetic solution.

I'm interested if someone has maybe tried with the current CVS version
with the KDE front-end i.e. can we expect that  KDE LyX version will solve
this problem as well as the problem with macron character in latin-2
fonts?

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sun, May 06, 2001 at 10:02:27AM +0200, Sasa Janiska wrote:
 On Sat, 5 May 2001, Matej Cepl wrote:
 
  I am a Czech user of the Lyx and I am very happy with that. Actually,
  setting of the keyboard is rather tricky. You have to switch OFF your
  main X keyboard (or change to English) and then set ON the Slovenian
  (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
  course, that you should have set characters to Latin-2.
 
 
 Do you use LyX under KDE?
 
 The problem is that finally under KDe 2.0.x I have Croatian characters
 (latin2) under KDE in all applications - except in LyX.

I did (now I switched to GNOME, because of excessive demands of KDE on 
the memory). However, I feel that there is really something screwed up 
in the KDE keyboard management (actually, it is the only thing which 
seemes to be actually worse than it was in KDE 1.1, where kikbd was the 
Great Thing). It helped me, to get rid of the KDE keyboard at all and 
use only X keyboard. Try these two steps:

1. set up your keyboard in XF86Config, so that it works well somewhere 
outside of KDE (try to log in GNOME or to Failsafe setting with 
RedHat). For me, this settings in XF86Config works:

**
# Keyboard section
# 
**

Section Keyboard

ProtocolStandard

AutoRepeat  500 5

#To set the LeftAlt to Meta, RightAlt key to ModeShift, 
#RightCtl key to Compose, and ScrollLock key to ModeLock:

LeftAltMeta
RightAltMeta
ScrollLock  Compose
RightCtlControl
  
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#XkbModelpc102
# If you have a US Microsoft Natural keyboard, you can use:
#XkbModelmicrosoft
#
# These are the default XKB settings for XFree86
XkbRulesxfree86
XkbModelpc105 # for no-name WinKeyboard
XkbLayout   czsk(cz_us_qwerty)
XkbOptions  grp:shift_toggle
XkbOptions  group_led

EndSection

RTFM for further information.

If you ceratin and confident, that you have pretty well working 
keyboard in xterm, you can continue to the next step.

2. Prevent KDE from screwing up things by comenting up the line 
soewhere in ./.kde/config/kcminput (but I cannot find it exactly now; 
any help?).
 
 If I want to have latin-2 characters in LyX, I have to sacrifice them in
 all other applications under KDE - it is not really cosmetic solution.

For me it was enough just to switch to English keyboard while using 
LyX and then to the Czech one when switched to some other application.

 I'm interested if someone has maybe tried with the current CVS version
 with the KDE front-end i.e. can we expect that  KDE LyX version will solve
 this problem as well as the problem with macron character in latin-2
 fonts?

And what about glyx? Anyone has any information?

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sat, 5 May 2001, Matej Cepl wrote:

 I am a Czech user of the Lyx and I am very happy with that. Actually,
 setting of the keyboard is rather tricky. You have to switch OFF your
 main X keyboard (or change to English) and then set ON the Slovenian
 (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
 course, that you should have set characters to Latin-2.


Do you use LyX under KDE?

The problem is that finally under KDe 2.0.x I have Croatian characters
(latin2) under KDE in all applications - except in LyX.

If I want to have latin-2 characters in LyX, I have to sacrifice them in
all other applications under KDE - it is not really cosmetic solution.

I'm interested if someone has maybe tried with the current CVS version
with the KDE front-end i.e. can we expect that  KDE LyX version will solve
this problem as well as the problem with macron character in latin-2
fonts?

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sun, May 06, 2001 at 10:02:27AM +0200, Sasa Janiska wrote:
 On Sat, 5 May 2001, Matej Cepl wrote:
 
  I am a Czech user of the Lyx and I am very happy with that. Actually,
  setting of the keyboard is rather tricky. You have to switch OFF your
  main X keyboard (or change to English) and then set ON the Slovenian
  (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
  course, that you should have set characters to Latin-2.
 
 
 Do you use LyX under KDE?
 
 The problem is that finally under KDe 2.0.x I have Croatian characters
 (latin2) under KDE in all applications - except in LyX.

I did (now I switched to GNOME, because of excessive demands of KDE on 
the memory). However, I feel that there is really something screwed up 
in the KDE keyboard management (actually, it is the only thing which 
seemes to be actually worse than it was in KDE 1.1, where kikbd was the 
Great Thing). It helped me, to get rid of the KDE keyboard at all and 
use only X keyboard. Try these two steps:

1. set up your keyboard in XF86Config, so that it works well somewhere 
outside of KDE (try to log in GNOME or to Failsafe setting with 
RedHat). For me, this settings in XF86Config works:

**
# Keyboard section
# 
**

Section Keyboard

ProtocolStandard

AutoRepeat  500 5

#To set the LeftAlt to Meta, RightAlt key to ModeShift, 
#RightCtl key to Compose, and ScrollLock key to ModeLock:

LeftAltMeta
RightAltMeta
ScrollLock  Compose
RightCtlControl
  
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#XkbModelpc102
# If you have a US Microsoft Natural keyboard, you can use:
#XkbModelmicrosoft
#
# These are the default XKB settings for XFree86
XkbRulesxfree86
XkbModelpc105 # for no-name WinKeyboard
XkbLayout   czsk(cz_us_qwerty)
XkbOptions  grp:shift_toggle
XkbOptions  group_led

EndSection

RTFM for further information.

If you ceratin and confident, that you have pretty well working 
keyboard in xterm, you can continue to the next step.

2. Prevent KDE from screwing up things by comenting up the line 
soewhere in ./.kde/config/kcminput (but I cannot find it exactly now; 
any help?).
 
 If I want to have latin-2 characters in LyX, I have to sacrifice them in
 all other applications under KDE - it is not really cosmetic solution.

For me it was enough just to switch to English keyboard while using 
LyX and then to the Czech one when switched to some other application.

 I'm interested if someone has maybe tried with the current CVS version
 with the KDE front-end i.e. can we expect that  KDE LyX version will solve
 this problem as well as the problem with macron character in latin-2
 fonts?

And what about glyx? Anyone has any information?

Matej

Re: latin2 keyboard in LyX 1.1.6fix1

[Sasa Janiska]

On Sat, 5 May 2001, Matej Cepl wrote:

> I am a Czech user of the Lyx and I am very happy with that. Actually,
> setting of the keyboard is rather tricky. You have to switch OFF your
> main X keyboard (or change to English) and then set ON the Slovenian
> (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
> course, that you should have set characters to Latin-2.
>

Do you use LyX under KDE?

The problem is that finally under KDe 2.0.x I have Croatian characters
(latin2) under KDE in all applications - except in LyX.

If I want to have latin-2 characters in LyX, I have to sacrifice them in
all other applications under KDE - it is not really cosmetic solution.

I'm interested if someone has maybe tried with the current CVS version
with the KDE front-end i.e. can we expect that  KDE LyX version will solve
this problem as well as the problem with macron character in latin-2
fonts?

Sincerely,
Sasa

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sun, May 06, 2001 at 10:02:27AM +0200, Sasa Janiska wrote:
> On Sat, 5 May 2001, Matej Cepl wrote:
> 
> > I am a Czech user of the Lyx and I am very happy with that. Actually,
> > setting of the keyboard is rather tricky. You have to switch OFF your
> > main X keyboard (or change to English) and then set ON the Slovenian
> > (or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of
> > course, that you should have set characters to Latin-2.
> >
> 
> Do you use LyX under KDE?
> 
> The problem is that finally under KDe 2.0.x I have Croatian characters
> (latin2) under KDE in all applications - except in LyX.

I did (now I switched to GNOME, because of excessive demands of KDE on 
the memory). However, I feel that there is really something screwed up 
in the KDE keyboard management (actually, it is the only thing which 
seemes to be actually worse than it was in KDE 1.1, where kikbd was the 
Great Thing). It helped me, to get rid of the KDE keyboard at all and 
use only X keyboard. Try these two steps:

1. set up your keyboard in XF86Config, so that it works well somewhere 
outside of KDE (try to log in GNOME or to "Failsafe" setting with 
RedHat). For me, this settings in XF86Config works:

**
# Keyboard section
# 
**

Section "Keyboard"

Protocol"Standard"

AutoRepeat  500 5

#To set the LeftAlt to Meta, RightAlt key to ModeShift, 
#RightCtl key to Compose, and ScrollLock key to ModeLock:

LeftAltMeta
RightAltMeta
ScrollLock  Compose
RightCtlControl
  
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#XkbModel"pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#XkbModel"microsoft"
#
# These are the default XKB settings for XFree86
XkbRules"xfree86"
XkbModel"pc105" # for no-name WinKeyboard
XkbLayout   "czsk(cz_us_qwerty)"
XkbOptions  "grp:shift_toggle"
XkbOptions  "group_led"

EndSection

RTFM for further information.

If you ceratin and confident, that you have pretty well working 
keyboard in xterm, you can continue to the next step.

2. Prevent KDE from screwing up things by comenting up the line 
soewhere in ./.kde/config/kcminput (but I cannot find it exactly now; 
any help?).
 
> If I want to have latin-2 characters in LyX, I have to sacrifice them in
> all other applications under KDE - it is not really cosmetic solution.

For me it was enough just to switch to English keyboard while using 
LyX and then to the Czech one when switched to some other application.

> I'm interested if someone has maybe tried with the current CVS version
> with the KDE front-end i.e. can we expect that  KDE LyX version will solve
> this problem as well as the problem with macron character in latin-2
> fonts?

And what about glyx? Anyone has any information?

Matej

latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Hello!

I have problems with making the Slovenian Latin-2 keyboard work
with LyX 1.1.6fix1.

I set my screen font encoding to iso-8859-2.  When I try to enter
"" (ie. I press the key labeled "" on my keyboard) nothing
happens.  If I substitute the keyboard with Latin-1, it gives the
correct Latin-2 characters on screen.

This is the output with "lyx -dbg key":

Setting debug level to key
Debugging `key' (Keyboard events handling)
Find a free buffer.
LyX: X11 color linen allocated for background
LyX: X11 color grey40 allocated for bottom area
LyX: X11 color black allocated for cursor
Workarea event: KEYBOARD
WorkArea: Key is `a' [97]
WorkArea: Keysym is `a' [97]
Using keysym [B]
Workarea Diff: 370383
KeySym is a[97] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][a]
LyX: X11 color black allocated for text
Workarea event: KEYBOARD
WorkArea: Key is `ccaron' [488]
WorkArea: Keysym is `ccaron' [488]
Using keysym [B]
Workarea Diff: 6890
KeySym is ccaron[488] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][ccaron]
Empty argument! - this is wrong!

... Now I substituted the keyboard with Latin-1 and pressed egrave:

Workarea event: KEYBOARD
WorkArea: Key is `egrave' [232]
WorkArea: Keysym is `egrave' [232]
Using keysym [B]
Workarea Diff: 4367
KeySym is egrave[232] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][egrave] -- this displays ccaron, not egrave


I read the i18n keyboard section in "Customizing LyX", but it didn't
give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
users that had a similar problems - could you, please, tell me what
to do?
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sat, May 05, 2001 at 06:24:54PM +0200, Roman Maurer wrote:
 I set my screen font encoding to iso-8859-2.  When I try to enter
 "" (ie. I press the key labeled "" on my keyboard) nothing
 happens.  If I substitute the keyboard with Latin-1, it gives the
 correct Latin-2 characters on screen.
 
 I read the i18n keyboard section in "Customizing LyX", but it didn't
 give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
 users that had a similar problems - could you, please, tell me what
 to do?

I am a Czech user of the Lyx and I am very happy with that. Actually, 
setting of the keyboard is rather tricky. You have to switch OFF your 
main X keyboard (or change to English) and then set ON the Slovenian 
(or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of 
course, that you should have set characters to Latin-2.

Hope it helps.

Matej

latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Hello!

I have problems with making the Slovenian Latin-2 keyboard work
with LyX 1.1.6fix1.

I set my screen font encoding to iso-8859-2.  When I try to enter
"" (ie. I press the key labeled "" on my keyboard) nothing
happens.  If I substitute the keyboard with Latin-1, it gives the
correct Latin-2 characters on screen.

This is the output with "lyx -dbg key":

Setting debug level to key
Debugging `key' (Keyboard events handling)
Find a free buffer.
LyX: X11 color linen allocated for background
LyX: X11 color grey40 allocated for bottom area
LyX: X11 color black allocated for cursor
Workarea event: KEYBOARD
WorkArea: Key is `a' [97]
WorkArea: Keysym is `a' [97]
Using keysym [B]
Workarea Diff: 370383
KeySym is a[97] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][a]
LyX: X11 color black allocated for text
Workarea event: KEYBOARD
WorkArea: Key is `ccaron' [488]
WorkArea: Keysym is `ccaron' [488]
Using keysym [B]
Workarea Diff: 6890
KeySym is ccaron[488] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][ccaron]
Empty argument! - this is wrong!

... Now I substituted the keyboard with Latin-1 and pressed egrave:

Workarea event: KEYBOARD
WorkArea: Key is `egrave' [232]
WorkArea: Keysym is `egrave' [232]
Using keysym [B]
Workarea Diff: 4367
KeySym is egrave[232] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][egrave] -- this displays ccaron, not egrave


I read the i18n keyboard section in "Customizing LyX", but it didn't
give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
users that had a similar problems - could you, please, tell me what
to do?
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sat, May 05, 2001 at 06:24:54PM +0200, Roman Maurer wrote:
 I set my screen font encoding to iso-8859-2.  When I try to enter
 "" (ie. I press the key labeled "" on my keyboard) nothing
 happens.  If I substitute the keyboard with Latin-1, it gives the
 correct Latin-2 characters on screen.
 
 I read the i18n keyboard section in "Customizing LyX", but it didn't
 give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
 users that had a similar problems - could you, please, tell me what
 to do?

I am a Czech user of the Lyx and I am very happy with that. Actually, 
setting of the keyboard is rather tricky. You have to switch OFF your 
main X keyboard (or change to English) and then set ON the Slovenian 
(or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of 
course, that you should have set characters to Latin-2.

Hope it helps.

Matej

latin2 keyboard in LyX 1.1.6fix1

[Roman Maurer]

Hello!

I have problems with making the Slovenian Latin-2 keyboard work
with LyX 1.1.6fix1.

I set my screen font encoding to iso-8859-2.  When I try to enter
"š" (ie. I press the key labeled "" on my keyboard) nothing
happens.  If I substitute the keyboard with Latin-1, it gives the
correct Latin-2 characters on screen.

This is the output with "lyx -dbg key":

Setting debug level to key
Debugging `key' (Keyboard events handling)
Find a free buffer.
LyX: X11 color linen allocated for background
LyX: X11 color grey40 allocated for bottom area
LyX: X11 color black allocated for cursor
Workarea event: KEYBOARD
WorkArea: Key is `a' [97]
WorkArea: Keysym is `a' [97]
Using keysym [B]
Workarea Diff: 370383
KeySym is a[97] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][a]
LyX: X11 color black allocated for text
Workarea event: KEYBOARD
WorkArea: Key is `ccaron' [488]
WorkArea: Keysym is `ccaron' [488]
Using keysym [B]
Workarea Diff: 6890
KeySym is ccaron[488] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][ccaron]
Empty argument! <- this is wrong!

... Now I substituted the keyboard with Latin-1 and pressed egrave:

Workarea event: KEYBOARD
WorkArea: Key is `egrave' [232]
WorkArea: Keysym is `egrave' [232]
Using keysym [B]
Workarea Diff: 4367
KeySym is egrave[232] State is [0]
action first set to [-1]
meta_fake_bit is [0]
action now set to [-1]
Key [-1][egrave] <-- this displays ccaron, not egrave


I read the i18n keyboard section in "Customizing LyX", but it didn't
give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
users that had a similar problems - could you, please, tell me what
to do?
-- 
Regards,
  Roman

Re: latin2 keyboard in LyX 1.1.6fix1

[Matej Cepl]

On Sat, May 05, 2001 at 06:24:54PM +0200, Roman Maurer wrote:
> I set my screen font encoding to iso-8859-2.  When I try to enter
> "š" (ie. I press the key labeled "" on my keyboard) nothing
> happens.  If I substitute the keyboard with Latin-1, it gives the
> correct Latin-2 characters on screen.
> 
> I read the i18n keyboard section in "Customizing LyX", but it didn't
> give me a clue.  Surely there are some Croat, Czech, Slovak and Polish
> users that had a similar problems - could you, please, tell me what
> to do?

I am a Czech user of the Lyx and I am very happy with that. Actually, 
setting of the keyboard is rather tricky. You have to switch OFF your 
main X keyboard (or change to English) and then set ON the Slovenian 
(or Czech, in my case) keyboard in LyX (via Edit/Preferences). Of 
course, that you should have set characters to Latin-2.

Hope it helps.

Matej