> On Mar 3, 2025, at 4:51 PM, tom ehlert via Freedos-devel
> wrote:
>
> Dear Bret,
>
>> I am still trying to develop a good infrastructure in the programs to handle
>> multiple languages, though -- one where I wouldn't necessarily need to be
>> very involved in the process of adding new lang
Hello Tom,
> Am 04.03.2025 um 00:42 schrieb tom ehlert via Freedos-devel
> :
>
> My suggestion would be to attach these language data to the end of the .exe
> file, so there is
> only one resource (the .exe file) to be managed. And updating the .exe also
> updates the language resource.
this
> Am 04.03.2025 um 00:37 schrieb Jerome Shidel via Freedos-devel
> :
>
> I actually started working on solving this issue a while back with the FD-NLS
> Desktop Application for Linux, Mac and Windows.
>
> https://up.lod.bz/FDNLS_LNX
That looks really promising. I'd like to have something of
>> It could also use some sort of compression people have around anyway, such
>> as GZ or ZIP :-)
> Sure it could use GZ. But that would blow up the code size by a factor of ten
> or more, I guess.
Many times more. There is no *one* ZIP or GZ compression alghorithm; there are
multiple differ
> On Mar 3, 2025, at 6:13 PM, Bernd Böckmann via Freedos-devel
> wrote:
>
> Hi Eric,
>
>> Is it possible to build the table when apps start
>
> The search table is a crucial part of the format, as it stores the offsets of
> the individual strings. So you cannot simply leave this out. But if
Hi Eric,
> Is it possible to build the table when apps start
The search table is a crucial part of the format, as it stores the offsets of
the individual strings. So you cannot simply leave this out. But if you
establish the hard requirements that every string does not contain but ends
with a
Hi, WilliOn Mar 3, 2025, at 3:10 PM, Wilhelm Spiegl via Freedos-devel wrote:a list of actual available translations is here: https://github.com/shidel/fd-nls/blob/master/report.txt.No period at the end. :-)https://github.com/shidel/fd-nls/blob/master/report.txtI always like the chart myself…https
yes, i noticed, when it was send. It is Carneval in Kiritz an der Knatter! and 24 x 24 is 576. Helau and Alaaf!--Gesendet mit der mail.com Mail AppAm 03.03.25, 22:45 schrieb Jerome Shidel via Freedos-devel lists.sourceforge.net>:
Hi, WilliOn Mar 3, 2025, at 3:10 PM, Wilhelm Spiegl via Freedos-devel
Hallo Willi,
ich habe vermutlich dieser Tage einen
KERNEL.SYS der nicht mehr mehr als 4G Files erzeugt
MOVE.EXE der Files > 2G verschieben kann.
Möchtest du die testen?
Tom
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https:/
Hi!
BTW, one option I was considering is a single .LNG file (or something)
with all the translations inside a single file instead of needing a
separate file for each language.
While this can be useful when clusters are large, I wonder about:
It is a binary format, basically consisting of a
Dear Bret,
> Am 03.03.2025 um 21:51 schrieb Bret Johnson via Freedos-devel
> :
>
> BTW, one option I was considering is a single .LNG file (or something) with
> all the translations inside a single file instead of needing a separate file
> for each language.
This is how we do it in SvarLANG,
Dear Bret,
> I am still trying to develop a good infrastructure in the programs to handle
> multiple languages, though -- one where I wouldn't necessarily need to be
> very involved in the process of adding new languages to a program. KITTEN
> really isn't that useful for me for multiple reaso
prinzipiell gerne. --Gesendet mit der mail.com Mail AppAm 03.03.25, 22:55 schrieb tom ehlert via Freedos-devel lists.sourceforge.net>:
Hallo Willi,
ich habe vermutlich dieser Tage einen
KERNEL.SYS der nicht mehr mehr als 4G Files erzeugt
MOVE.EXE der Files > 2G verschieben kann.
Möchtest du die
> What we would probably need is a Unix-style NLS system. under Unix you
> would have
>
> LANG=PT_PT.latin1
>
> or
>
> LANG=PT_BR.UTF8
>
> It's not only about messages in programs, but date formats, currencies etc.
That's changing the fundamental way DOS works. You're correct that all those
item
> It is not always just 2 letters. For example, Portuguese is PT and Brazilian
> Portuguese is PTBR.
Two thoughts this brings up. One is that we are not following the ISO
standard. Perhaps not a big deal, but that means we are on our own and will
definitely need to document everything to avoid
a list of actual available translations is here: https://github.com/shidel/fd-nls/blob/master/report.txt.it also shows the lang abbreviations that are actual in use.--Gesendet mit der mail.com Mail AppAm 03.03.25, 20:30 schrieb Danilo Pecher via Freedos-devel lists.sourceforge.net>:
What we would p
What we would probably need is a Unix-style NLS system. under Unix you
would have
LANG=PT_PT.latin1
or
LANG=PT_BR.UTF8
It's not only about messages in programs, but date formats, currencies etc.
On Mon, 3 Mar 2025 at 20:13, Jerome Shidel via Freedos-devel
wrote:
>
>
>
> > On Mar 3, 2025, at 1
> On Mar 3, 2025, at 12:51 PM, Bret Johnson via Freedos-devel
> wrote:
>
> I am trying to add international language support to at least some of the
> programs I am updating. So far, I have had some interaction with Thraex
> regarding French and Turkish translations for some of the program
I am trying to add international language support to at least some of the
programs I am updating. So far, I have had some interaction with Thraex
regarding French and Turkish translations for some of the programs, and am very
grateful for what he has provided thus far.
I am still trying to dev
19 matches
Mail list logo
