> > There are lots of ways to do this. In my case, I have over a thousand controls (sounds a lot, but > when you add up all the labels, group boxes etc!), so maintaining a perl hash becomes problematic - > ideally, the translations should be in a separate file or database, so they can be worked on > separately.
In that case, building the functionality might be a good way to go. However, to defend the case for the hash, if you were to generalize the names for all your scripts you *could* build the hash in a separate file and then 'require hashfile;'
