Too much for an INI file is 64kB. Unless you need a lot of text or have a lot of languages, you're not going to hit that mark.
And, yes, hash tables are faster since you don't have to keep reading the INI/text file when initializing a dialog. I didn't mention them simply because I felt it was easier to set the languages up in an INI file.
But, you could also set up a language-making dialog that will save it correctly for /hload as a hash table. If you took the time to do that, it would actually be much easier than setting it up in an INI file. You can create a dialog that shows the English words on one side and an edit box for the new words next to it. You fill in the words, hit ok and it saves it into a new hash table format that you can load.
Example Dialog:
******************************************************************
* Language: _______________ *
* *
* Yes __________________ *
* No __________________ *
* Would you like to play? __________________ *
* What is your password? __________________ *
******************************************************************
The idea is that you can then create multiple language files very quickly and easily.
Then, when you press OK (or after you go to however many NEXT pages you need to do all the words), it will /write the information to a text file (probably call it the name of the language you entered and maybe use an extension other than .txt so people aren't as likely to try messing with it) in the format of /hsave so that it can be loaded with /hload. Then, you can just use something like:
hload %language
did $dname 1 $hget(%language,1)
did $dname 2 $hget(%language,2)
Etc.
