Hi Jerome, >> That is a preview or technology demo, not a release.
Not joking... In the past, we had release candidates. This had the advantage that people were AWARE that by trying a RC, they made themselves a guinea pig of some experiment. There are not so many users who want to install FreeDOS and you certainly do not want to piss them off by declaring any experimental release as stable release and damaging stuff. >> Actually I have written a small (4 kB) tool for that in 2003 The binary is 3.7 kB, the zip is 16 kB including C source code and a little bit of documentation... Note that KITTEN and similar lightweight i18n / localization libraries also might be a nice idea for Mike to localize his TCP stuff :-) Also note that you are busy making a whole CD with FreeDOS stuff and that your current plan is to have a button which would install ALL source codes while even in Linux you only have buttons to install individual source packages for the few things that you want to recompile at any given moment. In short, do not worry about 16 kB if 1.6 GB are fine anyway. > vlocal default.en vecho "@WELCOME_MSG %OS_NAME% %OS_VERSION%" In the "classic" style of localized FreeDOS tools, you would not pass the name of a translated string text file as option. Instead, you would pass a PATH and a LANGUAGE as environment variables, which is more efficient. The software will look at PATH\NAMEOFTOOL.LANGUAGE and if that file is not found, it will fall back to compiled-in English strings. Localize, being a generic echo tool, has no compiled-in strings, so only there, you pass an English default on the command line. > type default.en | vstr /l 1 | vecho /i " %OS_NAME% %OS_VERSION%" You can reduce the number of steps: vstr /l 1 < %V8NLS%\default.%LANG% | vecho /i " %OS_NAME %OS_VERSION" However, I recommend to build vstr into vecho, because during install, you want to reduce pipe usage as far as possible :-) Note that classic FreeDOS style uses %NLSPATH% for directories (semicolon separated) which can contain localization text files, but I would not know how to parse that list in a batch context. Yet another reason why sometimes C is more convenient than BAT. Cheers, Eric ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
