Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!gmdzi!strobl From: strobl@gmdzi.UUCP (Wolfgang Strobl) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: WQVT Keywords: windows 3, WinQVT, kermit Message-ID: <3194@gmdzi.UUCP> Date: 10 Aug 90 10:55:16 GMT References: <11335@medusa.cs.purdue.edu> <417@philpav.UUCP> Organization: GMD, Sankt Augustin, F. R. Germany Lines: 44 lhv@philpav.UUCP (Leo H.Vermeulen) writes: >I would like to report two problems with WinQVT... >First problem: the program seems to have trouble understanding foreign >character sets. I have a PC on which Windows3 is set up to use the >Swedish character set. This means that the '/' character is under >shift-7, the '%' is under shift-5, and so on (don't ask me why, I'm >dutch, I'm just reporting the problem). Well, when typing shift-7 >what is echoed on my screen is '/&' (2 characters), these being the >characters that are assigned to shift-7 on an Swedish AND on a >American keyboard. Several other characters have a similar problem. >But then again, some don't. Does anyone have the same problem >(Germany?, Norway?) Yes. I tried WinQvt 4.30 and noticed the same behavior on my standard 102 key MF-II compatible German keyboard. The keys above 1234567890 (the shifted keys) should be !" $%&/()= on a German keyboard. ^ this was a ^U, which is the paragraph sign of the German typewriter. It is below 0x20, but printable. Really! Instead I get ! @" #' $ % ^ &/ * ( )= 1 2 3 4 5 6 7 8 9 0 > [second question deleted, I don't know the answer] >WinQVT is a thousandfold improvement over the brain-damaged VT100 >emulator that comes with Windows-3, and it's great to be able to >connect to Unix from within Windows, but I have still to meet a VT100 >emulator that does as good a job as Kermit does . What do you think I am using here? :-) MSDOS Kermit 3.01 runs quite well under Windows 3 in enhancede, in a window. But I would like to get a real Windows program with similar capabilities, because Kermit consumes too much cpu cycles (virtualization of old DOS applications is not that efficient under Windows 3), and because of the user interface. Wolfgang Strobl #include