Linux MS DOS discussions
 help / color / mirror / Atom feed
From: lars.bjorndal@broadpark.no (Lars Bjørndal)
To: linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: A dos character problem
Date: Tue, 17 Apr 2007 08:05:40 +0200	[thread overview]
Message-ID: <m3647v7cy3.fsf@fox.lamasti.net> (raw)
In-Reply-To: <c3d607cc0704141312x6fa6071ew8a690917429f5bf2@mail.gmail.com>

Bart Oldeman <bartoldeman@users.sourceforge.net> writes:

> On 4/13/07, Lars Bjørndal <lars.bjorndal@broadpark.no> wrote:
>> With all versions I've tried of Dosemu, I have problem with some
>> special characters. Now, I also tried the current svn version with the
>> same result.
>>
>> I'm a Norwegian using charset iso8859-1 and no-latin1 keyboard layout
>> on a Fedora core 6 system, and without GUI. The relevant settings in
>> dosemu.conf that's changed, is:
>>
>> $_rawkeyboard = (1)
>> $_internal_char_set = "cp850"
>
> Try to make sure you are *really* using iso8859-1. Fedora has
> everything UTF-8 by default so it's easy to miss out on something.
>
> On the Linux console, for non-suid DOSEMU you'd need
> a) locale settings without utf8 (output of "locale")
The relevant setting is 'LANG=no_NO.ISO8859-1' on this system.

> b) the console in 8-bit mode (using unicode_stop)

That's done in /etc/profile
> c) a good font. I sometimes do
>  setfont default8x16
>    to get at least all cp437 characters.

On my system, iso01.16 is used. I tried default8x16, but then the
norwegian character &oslash; didn't show correctly, at least not on my
braille display.

>   Although I just checked that LatArCyrHeb* at least works for your character.

Strange, not on my system. I switched to LatArCyrHeb-16 the char 179
is displayed as a question mark on my braille display (screen reader
is BRLTTY). I got a sighted person to check, and it's displayed like a
pentagon. It's displayed the same as Alt-178 also. Of course it's strange that
it's displayed as question mark on the braille display, since only
question mark is defined as question mark in the used braille table.
UTF-8 is not supported by BRLTTY.

>>     Character : ³ (0263, 179, 0xb3
>>     charset: eight-bit-graphic (8-bit graphic char (0xa0..0xff))
>>     code point: 179
>
> 0xb3 (or alt-179) produces a vertical bar in most DOS codepages (incl
> 437, 850, ..)

Ok, but it should not be displayed exactly as the normal vertical bar
|? It has to have it's own uniqe representation?

Is there other things to try?

Lars
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2007-04-17  6:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 14:11 A dos character problem Lars Bjørndal
2007-04-14 20:12 ` Bart Oldeman
2007-04-15  0:32   ` Tony Borras
2007-04-17  6:05   ` Lars Bjørndal [this message]
2007-04-18 14:56     ` Bart Oldeman
2007-04-18 20:49       ` Lars Bjørndal
2007-04-19  6:23         ` Lars Bjørndal
2007-04-20 14:05           ` Bart Oldeman
2007-04-24 21:04             ` Lars Bjørndal
2007-04-24 22:29               ` Andrew Brooks
2007-05-08 18:52                 ` 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=m3647v7cy3.fsf@fox.lamasti.net \
    --to=lars.bjorndal@broadpark.no \
    --cc=linux-msdos@vger.kernel.org \
    /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