>> under
>> what circumstances this is relevant so we can reproduce the problem
>> and it's solution.

> We've already showed you the problem and how to fix it.  With
> MKEYB, the Euro character is not generated correctly unless the Code
> Page is one where the Euro symbol is ASCII 213.  This is true for
> some Code Pages but not others.  That's a problem which you can
> easily reproduce yourself.  The solution is for MKEYB to be aware of
> the current Code Page instead of ignoring it,

how would MKEYB detect that code point 213 represents dotless i or €,
or what the correct code point for € is in the new selected codepage?
and how about äÄáàâÁÀÂ?


>  or at least warning
> the user that if they use the wrong Code Page some things may be displayed 
> incorrectly.

a pop up messagen Box "you have choosen to change the codepage, so €
no longer looks like €" ?

in fact MKEYB already warns the user by showing a  ı if the wrong
codepage is selected.

in fact an american who has never seen an international US-ASCII
keyboard (or even an Euro note) is probably not the right person to
argue here.

Tom



_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to