Hi, with the install scripts of Bernd and Jeremy in mind, I have
written a LOCALIZE tool (3.5k UPXed com, can certainly be even smaller).
It is basically KITTEN (the version which I use in FIND, not Toms original
one) with a command line interface.


http://www.coli.uni-sb.de/~eric/stuff/soft/



Usage example:

LOCALIZE 1.3
if [%errorlevel%]==[1] echo Your menu options are:
LOCALIZE 1.4 (1)
if [%errorlevel%]==[1] echo SOMETHING NICE (1)
LOCALIZE 1.5 (2)
if [%errorlevel%]==[1] echo SOMETHING ELSE (2)
choice /c:12


...

localize.en for the above example:

1.1:Your current language setting is:
1.2:Welcome at the SOMETHING batch script
1.3:Your menu options are:
1.4:Something nice
1.5:Something else
99.0:Prints a localized message (from localize.*)
99.1:Prints message number x.y (and echoes the [etc.])
99.2:Errorlevel: 0 if okay, 1 if no localize.* found.

and a German localize.de for the same example:

1.1:Deine aktuelle Spracheinstellung ist:
1.2:Willkommen bei IRGENDEINEM Batch Skript
1.3:Deine Auswahl ist:
1.4:Irgendwas NETTES
1.5:Irgendwas ANDERES
99.0:Zeigt einen lokalisierten Text an (aus localize.*)
99.1:Zeigt Text nummer x.y (und dann das [etc.])
99.2:Errorlevel: 0 wenn okay, 1 wenn kein localize.* gefunden.




The 99.* messages are for the help screen of localize itself.
The 1.1 and 1.2 messages are not used in the above snippet, but
they are used in the longer example that comes with localize.

Feel free to send contributions, e.g. more translations of the
help screen, code and translations for a more verbose help screen,
even smaller implementations of LOCALIZE, and so on. I think it is
good enough for the bootable FreeDOS installer CD already, so I am
not planning to do lots of work on localize myself soon. The installer
CD currently uses several batch files with lots of variables, calls,
ifs and gotos. And that only for the first few questions during the
installation process (later, a binary installer software takes over).

Have fun... .

Eric (eric -at- CoLi.Uni-SB.DE)