> On Sun, Aug 1, 2021 at 1:39 PM tom ehlert wrote:
> >[..]
> > KITTENC - catgets/kittengets compatible resource compiler
> >
> > KITTENC 'compiles' language resources to strings and attaches
> > these strings to the executable program such that the program can
> > retrieve these strings at
Hi Tom
On Sun, Aug 1, 2021 at 1:39 PM tom ehlert wrote:
>[..]
> KITTENC - catgets/kittengets compatible resource compiler
>
> KITTENC 'compiles' language resources to strings and attaches
> these strings to the executable program such that the program can
> retrieve these strings at execu
>> I think using language catalogs is a very flexible way to provide
>> internationalization in a program.
YES (see below)
>> The tradeoff is a bit of
>> performance (reading the catalog) and some extra code to manage
>> everything.
it makes no difference if you load your messages from your exe
> On 8/1/2021 10:03 AM, Robert Riebisch wrote:
> >
> > If we would streamline the build process for most of the FreeDOS tools,
> > creating per-language binaries will be a breeze.
On Sun, Aug 1, 2021 at 12:55 PM Ralf Quint wrote:
>
> It would be as simple as putting all files that do have transla
Hi Ralf,
>> If we would streamline the build process for most of the FreeDOS tools,
>> creating per-language binaries will be a breeze.
> It would be as simple as putting all files that do have translations for
> a specific language in a designated folder for that language, replace
> the text to
Well, I originally said the use case was "how to get a list of extended
ASCII characters into a file on FreeDOS" .. so really, I mean *extended*
ASCII here. And yes, any code less than 0 or greater than 255 is not valid
extended ASCII, so that's why I print those invalid code requests as '?' to
ind
On 8/1/2021 10:03 AM, Robert Riebisch wrote:
If we would streamline the build process for most of the FreeDOS tools,
creating per-language binaries will be a breeze.
It would be as simple as putting all files that do have translations for
a specific language in a designated folder for that lang
Hi Robert,
>
> Could you please specify the "some extra code to manage everything" in
> bytes? Just curious. Is it ~500 or ~2,500?
>
I just did a quick compile of the kitten test program with gcc-ia16 and found
that
without upx packing the sizes were as follows:
With kitten
11264 bytes
With
Hi Jim,
> So if you want to print out the degree symbol (ASCII decimal 248) you
> would type:
>
> char 248
>
> (ASCII codes not in 0-255 are printed as '?' instead.)
Would ASCII codes "not in 0-255" still be ASCII codes? ;-)
Original ASCII is only 128 chars, by the way.
Cheers,
Robert
--
Hi Ralf,
>> But for a modern DOS that needs to support different languages by
>> different users in different countries, I think language catalogs (the
>> "Kitten" method) provide the best solution.
>
> Well, the problem is that this can increase the size of a lot of
> executables by a lot. And
Hi Jim,
> I think using language catalogs is a very flexible way to provide
> internationalization in a program. The tradeoff is a bit of
> performance (reading the catalog) and some extra code to manage
> everything. The benefit is you end up with *one* compiled program that
> you use in every la
11 matches
Mail list logo
