pierre@imag.UUCP (Pierre LAFORGUE) (12/10/87)
NCSA Telnet is really a must, but ...
on a Mac SE and a Mac II, NCSA Telnet 2.0 forces an american keyboard, in a
permanent manner (it remains after exiting telnet, until the next Macintosh
reboot). It is very painful when you use, for instance, a french keyboard:
not only you have to remember to type Q for A, and so on, but you cannot
type for example a Control-Z under telnet.
[On a Macintosh +, one do not loss its keyboard]
Is this bug fixed in the last version ?
--
Pierre Laforgue pierre@imag.imag.fr {uunet.uu.net|mcvax}!imag!pierre geirp@IFI.UIO.NO (12/16/87)
>on a Mac SE and a Mac II, NCSA Telnet 2.0 forces an american keyboard, in a >permanent manner (it remains after exiting telnet, until the next Macintosh >reboot). This has to do with the way NCSA telnet uses key scripts. It has it's own KCHR resources to (I think) map cloverleaf-x to ctrl-x. The resource that is found in the program is tailored to US keyboards.The format of this resource is said to be found in technote no 160. The reason the keyboard remains in US mode after exiting NCSA telnet is that the program on exit sets the KCHR resource to the resource with id 0. (Insted of resetting it to its original value.) This is the resource for US keyboards. The solution is to past your local KCHR resource (found in System) into NCSA telnet and renumber it to have id 0. (You probably must use both REdit and ResEdit to do this.) A similar problem is that under MultiFinder the KCHR resource set by NCSA telnet remains in effect when NCSA telnet is deactivated. Regards, Geir Pedersen University of Oslo, Computing Service Phone +47-2-455731