Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Baurjan Ismagulov <ibr@gantek.com>
To: linux-msdos@vger.kernel.org
Cc: solt@eatpbank.ru
Subject: Re: using Turkish in dosemu
Date: Thu, 20 Jun 2002 14:47:10 +0300	[thread overview]
Message-ID: <20020620114709.GB10172@gantek.com> (raw)
In-Reply-To: <87ptyma6hx.fsf@eatpbank.ru>

On Thu, Jun 20, 2002 at 09:01:14AM +0400, Sergey Suleymanov wrote:
>  Baurjan> Unfortunately, no :( (tried both default
>  Baurjan> compiletime-settings and compiletime-settings.devel).
> 
>         Strange. It should fix loading external keytable with "load
>         <keymap>". 

The only difference was that pressing altgr-[ produces 159 (small s with
cedilla) instead of 156 (pound sign), which is printed without the patch
-- while both of these are not what I want.

I've started to think that my dosemu tr keymap is wrong. I list 857
codes there; shoudn't I? Sergey, if you are able to produce small o with
diaeresis, could you please send your loadkeys and dosemu keymaps?


>         Was patch applied without reject? Did you do make mrproper?

Yes. Yes.


>         Can you mail me -D+k debug output?

Here are some interesting lines:

config.term_charset=2
keyb_config_charset=terminal_cp437
paste_charset=iso8859-1
keyb_charset=iso8859-1
keynum->keysym: 33->00f6

Keynum 0x33 is comma (the key between m and period), isn't it? And
0x00f6 is utf-8 code for small o with diaeresis, isn't it? If so,
shouldn't it be 0x0094 (odiaeresis in 857)? I use "keycode 51 = 148
less" in the kernel keymap, and the following in dosemu keymap:

keytable keyb-user {
  0=
     0,27,"1234567890*-",127,9,
     "qwertyu",141,"op",167,129,13,0,"as",
     "dfghjkl",159,"i",130,0,44,"zxcv",
     "bnm",148,135,".",0,"*",0," ",0,0,0,0,0,0,
...

And are those cp437 / iso8859-1 settings important? Should they be set
to cp857 / iso8859-9, or that requires extra hacking?


>         BTW, you can check keytable with dosemu -I 'keytable dump
>         <filename>' It's name should be keyb-user.

dosemu.bin -I 'keytable dump tr' didn't show any keyboard-related info,
and dos session didn't start.


>         "echo -ne '\033(K'" or "charset G0 cp437" enables IBM Codepage
>         437 mapping to Unicode. I think codepage 437 is not the same
>         as codepage 857, isn't it?

Yes, these are different.


With best regards,
Baurjan.

  parent reply	other threads:[~2002-06-20 11:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-16 16:53 using Turkish in dosemu Baurjan Ismagulov
2002-06-17  5:57 ` Sergey Suleymanov
2002-06-17 11:38 ` Baurjan Ismagulov
     [not found]   ` <87elf6w0rx.fsf@eatpbank.ru>
2002-06-17 13:34     ` Baurjan Ismagulov
     [not found]       ` <87bsa93y95.fsf@eatpbank.ru>
2002-06-18 10:15         ` Baurjan Ismagulov
2002-06-18 13:25           ` Sergey Suleymanov
2002-06-19 15:01             ` Baurjan Ismagulov
     [not found]               ` <87ptyma6hx.fsf@eatpbank.ru>
2002-06-20 11:47                 ` Baurjan Ismagulov [this message]
     [not found]                   ` <87sn3hjihf.fsf@eatpbank.ru>
2002-06-21 13:48                     ` Baurjan Ismagulov
     [not found]                       ` <876609qjjk.fsf@eatpbank.ru>
2002-06-24 18:43                         ` Baurjan Ismagulov
2002-06-25 22:21                           ` Bart Oldeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020620114709.GB10172@gantek.com \
    --to=ibr@gantek.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=solt@eatpbank.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox