> On Jan 2, 2019, at 4:05 PM, stecdose <[email protected]> wrote: > > >>> * If the installation language is Russian, the text is garbled, no >>> Cyrillic letters are displayed. >> Yeah, that’s a known issue. Cant really think of a “good” way to solve it. >> >> Here’s the problem. >> >> Language and translation change when that language is highlighted on the >> menu. However, the Language settings, Codepage and font are not set until >> that language is actually selected. >> This requires loading some TSRs. They may be a way to unload them. But, I >> don’t know if or what it is. >> >> I have a bunch of stuff I’ve written over the years that can load fonts. >> Most recently are the QFONT tools included with PGME. They can convert >> to/from simple bit fonts, load qfonts temporarily, or turn them into a TSR. >> I may do something there to temp load/unload the Russian font on the menu. > > Maybe storing the codepage and font information are stored along with the > langua/keyboard layout is good. > > This way a small utility ("loadfont") can be called when changing language. > This would be good for all languages that have special letters.
Not a bad idea. But, not necessary. FDI is already designed to run a language specific SETLANG.BAT that has any settings and programs needed for a selected language. The issue is switching temporarily to highly different possibilities prior to selection. More specifically, unloading settings made from the previous highlight. Mostly,it is not an issue for most of the languages supported by FDI. However, Russian requires it. So, each time you scroll onto and off of the language, you would end up loading one codepage on top of another, and another and another. As a native English speaker, I really never had to mess around with those. There may be a way to unload one. But I am unaware of it. I don’t have the time or desire to RTFM it. It would just be quicker and easier to just extract the required fonts from their codepage, convert to my QFONT format, and use my loader to temporary load any font using no TSR or memory. That solution has one drawback, either limit fonts to only EGA or VGA sizes... Or, provide two sets for each language and detect/select the appropriate one. > >> >> I still need to do some more work in FDI to be able to handle installation >> from LiveCD-Type2. >> >> LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and >> Community to decide which will be the LiveCD. >> > Looking forward to it :) > :-) > > Nils > Jerome _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
