> 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 <freedos...@gmail.com> wrote: > > 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 be translated (and also paying attention to input checks > that are changing due to the different language) and recompile. > > Or we do it the 1990s way: Translators patching English binaries with a > > hex editor... (Requires un- and repacking with UPX.) > > Disregarding the need for using UPX in the first place, that would be > the least favorable solution of all. And absolutely no need as we should > have the translatable source code to begin with... Others are certainly welcome to create a new internationalization method, which might be completely different from the Cats/Kitten method. The original "Cats" library was written in 2000 to replicate the Unix catgets message catalog system - for example, to ease porting of Linux programs to FreeDOS. I used it in my programs at the time to support multiple spoken languages. Until then, I think only a few FreeDOS programs supported any kind of internationalization, and IIRC most of these required a compiled binary for each spoken language. The Cats implementation was later improved on by others to create a simpler, smaller "Kitten" library with wrappers that made it compatible with Cats. If there's a more efficient way to do this, please create it. Jim _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
