console font problem not eliminated

console font problem not eliminated

[Claudia Neumann]

Hi all, hi Bart,

I upgraded to dosemu-1.1.4.9 and used your patch, but  - I am sorry to say - 
it didn't change anything. In the Norton Commander the vertical lines are 
still big i and the horizontal lines -, the edges use some sort of A.

Shall I use same other console font?

Regards

Claudia 

Re: console font problem not eliminated

[Bart Oldeman]

On Thu, 30 Jan 2003, Claudia Neumann wrote:

> I upgraded to dosemu-1.1.4.9 and used your patch, but  - I am sorry to say -
> it didn't change anything. In the Norton Commander the vertical lines are
> still big i and the horizontal lines -, the edges use some sort of A.

Can you try with

$_term_char_set="ibm"
$_external_char_set = ""
$_internal_char_set = ""

That works for me now (with that patch).

> Shall I use same other console font?

no, if dosemu-1.0.2 worked your font should be OK.

Bart

Re: console font problem not eliminated

[Stas Sergeev]

Hello.

Bart Oldeman wrote:
> $_term_char_set="ibm"
> $_external_char_set = ""
> $_internal_char_set = ""
> That works for me now (with that patch).
Hmm, this doesn't look correct.
At least for those who have different
internal and external charsets (me)
this doesn't work.
IIRC Eric suggests to comment out
$_term_char_set entirely and use
only other two options, which is
what works for me perfectly.
So, unless I am missing something,
$_term_char_set is absolete and is
used in the new kbd code only for
compatibility purposes (is this correct?)

Re: console font problem not eliminated

[Bart Oldeman]

On Fri, 31 Jan 2003, Stas Sergeev wrote:

> Bart Oldeman wrote:
> > $_term_char_set="ibm"
> > $_external_char_set = ""
> > $_internal_char_set = ""
> > That works for me now (with that patch).
> Hmm, this doesn't look correct.
> At least for those who have different
> internal and external charsets (me)
> this doesn't work.

yes, but I was just trying to ask about the simplest configuration for
terminal-in-console for which you should be able to get the box
characters.

> IIRC Eric suggests to comment out
> $_term_char_set entirely and use
> only other two options, which is
> what works for me perfectly.
> So, unless I am missing something,
> $_term_char_set is absolete and is
> used in the new kbd code only for
> compatibility purposes (is this correct?)

essentially, yes. $_term_char_set = "ibm" is equivalent to:
$_external_char_set = "cp437"
$_internal_char_set = "cp437"
also, if *everything* is commented out then "ibm" is the default on the
console (latin is the default via network or xterm).

The bug was that with $_external_char_set = "cp437", DOSEMU forgot to do
the equivalent of
echo -e '\033(U'
which effectively selects cp437 on the Linux console.

This doesn't seem to help the OP though ...

Bart