So, it sounds like Eric would suggest just sticking with two-letter language
codes for LANG, use LANG if it exists (without any verification testing), and
maybe have a command-line override switch?
___
Freedos-devel mailing list
Freedos-devel@lists.so
On Tue, 10 Aug 2021, Bret Johnson wrote:
The problem with this approach is something like Belgium. Somebody
correct me if I'm wrong, but Belgium does not have its own language --
some parts of the country are French and other parts are German. There
is a Belgian country code and a Belgian ke
Hi Bret,
> https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
I would say the FreeDOS tradition is to use 2 letter codes
without explicitly specifying the intended codepage, because
both setting LANG and loading the codepage are typically
done in config and autoexec and it is easy to edit bo
I've been working with Thraex on the translations of my PRTSCR program to
French and Turkish. I want to thank Thraex for volunteering, and am still
working through the technical details on implementation. I've ran into a few
items that I would like some opinions on how to handle them. These h
Hi,
After creating a VM with VirtualBox 6.1.22_Ubuntu r144080 under Ubuntu
20.04, I did a full install of FreeDOS 1.3 RC4 from the Live CD. Then,
with FDIMPLES I installed all networking programs with, amongst them,
the Crynwr drivers.
I found the CRYNWR.BAT file that is in the fdos\drivers\crynw
>>> you can design APIs all day long, but if nobody is using these APIs
>>> it's a bit pointless. and the BIOS certainly will not suddenly call
>>> any DMA reservation API.
>> These APIs will be used by anybody who needs to virtualize things
>> like IRQs, I/O ports, and DMA channels.
> after mo
>> you can design APIs all day long, but if nobody is using these APIs
>> it's a bit pointless. and the BIOS certainly will not suddenly call
>> any DMA reservation API.
> These APIs will be used by anybody who needs to virtualize things
> like IRQs, I/O ports, and DMA channels.
after more then
> you can design APIs all day long, but if nobody is using these APIs
> it's a bit pointless. and the BIOS certainly will not suddenly call
> any DMA reservation API.
These APIs will be used by anybody who needs to virtualize things like IRQs,
I/O ports, and DMA channels.
> besides this, MSDOS a
Hallo Herr tom ehlert,
am Dienstag, 10. August 2021 um 11:04 schrieben Sie:
>>> however if several applications want to access the same DMA controller
>>> at the sam time things get complicated. there is no communication
>>> between these applications.
>> Exactly. That's what the API would som
>> however if several applications want to access the same DMA controller
>> at the sam time things get complicated. there is no communication
>> between these applications.
> Exactly. That's what the API would somehow need to manage.
you can design APIs all day long, but if nobody is using th
10 matches
Mail list logo
