console font problem not eliminated
Hello.
Quoted 4 lines · Bart Oldeman
$_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?)
Quoted 9 lines · Stas Sergeev
Quoted 4 lines · Bart Oldeman
$_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.
Quoted 8 lines
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