Hi all!
Saluton amiko!
Before I forget, I noticed that you do use ISO codepages.
I'll work on distinct packs of codepages and keyboard layouts for ISO
8859-1 ~ 16.
>> While Unicode is huge, DOS keyboard layouts tend to be limited to
>> Latin and Cyrillic and some other symboly which is a tiny sub
Hi,
On 7/5/11, Henrique Peron wrote:
>
> Before I forget, I noticed that you do use ISO codepages.
> I'll work on distinct packs of codepages and keyboard layouts for ISO
> 8859-1 ~ 16.
Honestly, I very rarely use only Latin-3 (913), so please don't waste
500 hours on my account! ;-) It's ve
Saluton!
Em 05/07/2011 18:25, Rugxulo escreveu:
>> Before I forget, I noticed that you do use ISO codepages.
>> I'll work on distinct packs of codepages and keyboard layouts for ISO
>> 8859-1 ~ 16.
> Honestly, I very rarely use only Latin-3 (913), so please don't waste
> 500 hours on my account!
Saluton,
On 7/6/11, Henrique Peron wrote:
>
> Em 05/07/2011 18:25, Rugxulo escreveu:
>>
>> Honestly, I very rarely use only Latin-3 (913), so please don't waste
>> 500 hours on my account! ;-) It's very low priority.
>
> My friend, it is always a pleasure. I do hope that end-users have as
> m
Hi
I don't know much (anything) about unicode but,
Right-to-left might be hard to do (I guess?), but technically as long
as they can see and enter what they want, I'm sure they can get used
to left-to-right.
>>> Excuse me? How can anyone type the arabic, syriac or hebrew abjads fr
Hi Jeffrey,
> Would chaining interrupt 0x10 be reasonable? If I am not mistaken the FreeDOS
> kernel
> uses interrupt 0x10 function 0x0E to print characters to the screen. A TSR
> could be
> written to handle function 0x0E and pass the other functions to the BIOS.
Of course. In the old days of
Hi Eric,
> HOWEVER, the array, int 10 and CON are all officially assuming a
> "one byte is one character" scenario so your layout is likely to
> get messed up when you use UTF-8 and you cannot use UTF-16 anyway.
In color text modes, alternating bytes are used for character and attribute.
So if you
Hi Jeffrey,
>> HOWEVER, the array, int 10 and CON are all officially assuming a
>> "one byte is one character" scenario so your layout is likely to
>> get messed up when you use UTF-8 and you cannot use UTF-16 anyway.
> In color text modes, alternating bytes are used for character and attribute.
Hi Eric,
My main point was to use 0x10 to allow right to left display of Unicode for
Arabic, Syriac, Hebrew etc. If each application processes its own input and
output
and we are only concerned with displaying their output, then whether they use
0x10 or write directly to video memory is irrelevan
Hello,
2011/7/7 Eric Auer :
> Still I think UTF-8 aware KEYB and DISPLAY together with old apps
> are still a lot more useful than any "you always have to use 16 bit
> wide characters" method which would only work with new apps at all.
KEYB would need no changes, 2-char wide characters would be a
> Appart from turning DISPLAY into a DOS device driver and override
> kernel's CON, but not only IOCTL, but also write.
FWIW, you don't actually need to turn DISPLAY into a device driver in order to
replace/enhance CON. You can do that with a TSR also. See my USBPRINT if you
want an example of
I'm curious, you check the LoL to get the pointers and override it?
Aitor
2011/7/10 Bret Johnson :
>> Appart from turning DISPLAY into a DOS device driver and override
>> kernel's CON, but not only IOCTL, but also write.
>
> FWIW, you don't actually need to turn DISPLAY into a device driver in or
> I'm curious, you check the LoL to get the pointers and override it?
No, you just insert a new one with the same name in the Device Driver chain.
DOS always searches the chain in order, and uses the first one with the correct
name that it finds. It doesn't actually know, or even care, where t
Ok, sorry, that's what I meant. That you find the chain at the List of
Lists, right?
Aitor
2011/7/10 Bret Johnson :
>> I'm curious, you check the LoL to get the pointers and override it?
>
> No, you just insert a new one with the same name in the Device Driver chain.
> DOS always searches the c
> Ok, sorry, that's what I meant. That you find the chain at the List
> of Lists, right?
Yes. The first Device Driver header (NUL) is in the LoL. From there, you can
follow the chain (a linked list of pointers) as far as you want, and can
insert/remove new headers wherever you want.
15 matches
Mail list logo
