> Only highly desirable to those who don't use screen readers.
>
> Using a graphical mode but simulating a text mode would not work for
> anyone using a screen reader, since there's no possible way for the
> screen reader to "read" the graphical screen.
Actually, there is a way. I've never used a
On 10/11/2021 3:43 PM, Aitor Santamaría wrote:
By definition, anything above 127 is not ASCII, so it will depend
on the codepage. Still, it is extremely rare that people use more
than one codepage on the same system AND have identical characters
with different byte values depending
On Mon, 11 Oct 2021 at 22:25, Aitor Santamaría wrote:
>
> Yeah, good to clarify. It does work (with either FD-KEYB or MKEYB).
>
> The question in discussion here is: if you later want to change to, say,
> codepage 850:
> (a) with FD-KEYB, you issue KEYB UK,850,,C:\DOS\KEYBOARD.SYS (no reboot)
>
Hi,
On Mon, 11 Oct 2021 at 22:18, Liam Proven wrote:
> A question:
>
> Does the old MS-style
>
> [
> [CONFIG.SYS]
>
> country=044,437,c:\dos\country.sys
>
> [AUTOEXEC.BAT]
>
> keyb uk,437,c:\dos\keyboard.sys
> ]
>
> ... config still work? If not, would it work if the files were copied
> from MS-
On Mon, 11 Oct 2021 at 21:19, E. Auer wrote:
>
> By definition, anything above 127 is not ASCII, so it will depend
> on the codepage. Still, it is extremely rare that people use more
> than one codepage on the same system AND have identical characters
> with different byte values depending on whic
> send a keyboard code �
That doesn't always work work. Let me use a Star Trek analogy (I hope most
people can relate to this).
Let's say someone in the Enterprise wants to get down to a planet that the Star
Ship is circling. There are two ways they can do this. One is to use the
Transport
Hello Eric,
On Mon, 11 Oct 2021 at 21:19, E. Auer wrote:
> > Again, you're misunderstanding the problem. You shouldn't just
> > automatically generate an ASCII 213 no matter what the Code Page is --
> > you should only generate an ASCII 213 when that's the Euro character
> > on the Code Page cu
Hi!
now they will generate 213 with AltGr+E, whatever the codepage. with
a proper codepage, this will look like €.
Again, you're misunderstanding the problem. You shouldn't just
automatically generate an ASCII 213 no matter what the Code Page is --
you should only generate an ASCII 213 when
Hi,
On Mon, 11 Oct 2021 at 17:26, Bret Johnson wrote:
> For older versions of FD-KEYB and KEYB programs from other places
> (including MKEYB), I was thinking of maybe doing something with an
> Environment variable, similar to what FreeDOS has implemented with the
> COUNTRY environment variable.
> Well, a summary for both: I was thinking of providing an interface
> to actually return the KeybCB, you'd have all the information (but
> would be given the chance to mess around with it) :)
> With that you have the entire Scancode-to-codepage (rather than
> ASCII-to-scancode).
Thanks, Aitor.
>> So you made up your own GR mapping that is different than everybody
>> else's (there is a "Tom's custom GR keyboard layout")?
> of course not.
Exactly. This was me responding to you saying there were no standards, but you
followed a standard (whether de facto or explicitly documented, still
11 matches
Mail list logo
