On 24/06/2023 02:18, Michael Brutman via Freedos-user wrote:
A centralized mapping would be nice, but then you will run into the
question of how strict you want the code to be.
In an ideal world, one could imagine a new nlsfunc service that answers
with a best effort match from the local codep
I added some limited Unicode support to mTCP Telnet and mTCP IRCjr in the
last release a few months ago.
- I used a text file to store the mapping. That lets people add code
points or make corrections if they don't like the choices I made.
- The code uses the text file both ways; to figu
On 23/06/2023 01:02, Eric Auer wrote:
PS: For all things NOT mentioned above, I expect no support for
Unicode or conversions at all. I expect those to just assume an
8-bit encoding in text (and file names) matching your codepage.
For the sake of completeness I will add that AMB has "some" UTF-8
Hi all,
as part of a mail with Vacek, I made a list of apps from
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/report.html
which MIGHT have some sort of Unicode and codepage awareness:
By that, I mean that those apps can process input and/or output
which are en
My FLTK/Xlib port supports Unicode and truetype fonts. This allows to use
Unicode character sets with DJGPP.
Georg
http://code.google.com/p/nanox-microwindows-nxlib-fltk-for-dos/
--
For Developers, A Lot Can Happen In
Hi,
On Fri, Apr 13, 2012 at 9:33 AM, Alex wrote:
>
> Just to save me some time, instead of going through all the forums and
> the documentation files (which would take forever), I ask this
> question to you all: which of the (FreeDOS-based) languages support
> Unicode?
>
> More specifically, does
El 13/04/2012 10:14 a.m., Mateusz Viste escribió:
> I doubt you will find any DOS language that supports Unicode 'out of the box'.
> However, there are Unicode-enabled DOS programs out there, so I'd say your
> best shot is to take a look inside them.
>
> Blocek is a unicode editor written in Pasca
El 13/04/2012 10:03 a.m., Alex escribió:
> Just to save me some time, instead of going through all the forums and
> the documentation files (which would take forever), I ask this
> question to you all: which of the (FreeDOS-based) languages support
> Unicode?
>
> More specifically, does anyone know
I doubt you will find any DOS language that supports Unicode 'out of the box'.
However, there are Unicode-enabled DOS programs out there, so I'd say your best
shot is to take a look inside them.
Blocek is a unicode editor written in Pascal:
http://www.laaca-mirror.ic.cz/
FoxType is a UTF8 text v
Just to save me some time, instead of going through all the forums and
the documentation files (which would take forever), I ask this
question to you all: which of the (FreeDOS-based) languages support
Unicode?
More specifically, does anyone know if Turbo Pascal can support UTF-8?
Is there any lib
I'll try it and let you know.
Meanwhile, let me tell you that I'll need room for 142 strings.
I explain.
VISCII (Vietnamese Extended ASCII) comprehends all the set of 134
precomposed vietnamese accented letters. I made it available for FreeDOS
(along with the corresponding keyboard layout) a l
That should work, try it out and let me know.
There's a bug with strings that I am fixing already, though. If it
doesn't work, I'll have the 2.01 beta soon.
Aitor
2011/7/9 Henrique Peron :
> Hi all,
>
>>> Still I think UTF-8 aware KEYB and DISPLAY together with old apps
>>> are still a lot more u
> Most programs could already be loaded earlier in CONFIG.SYS if they
> were adjusted in that way, though some of the DOS structures aren't
> available yet in that case.
That's one of the big advantages of TSR's, in my opinion. While CONFIG.SYS is
being processed, DOS is not yet "all there". As
> 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.
> IMHO, TSR's have a lot of advantages over device drivers, and can still be
> installed in CONFIG.SYS if you actually want/need to do that (with the
> INSTALL= option).
You can even write a single executable which can be loaded both as "device
driver" (DEVICE= or DEVLOAD) and as normal program (I
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
> 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
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
> 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
Hi all,
>> 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 String.
> True
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
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
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,
> 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,
> 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
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
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
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!
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
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
30 matches
Mail list logo
