From: Christopher Smith <[EMAIL PROTECTED]> Gabriel Sechan wrote: > In 99% of apps, internationalization is overkill. Unless a human is > meant to be editing the file (such as a config file), its just a waste > of CPU power and time. Okay, that part I'd disagree with. Anytime you have strings as your data type, there is a distinct possibility you will need some kind of internationalization. It's not a given, but it applies to far more than 1% of the cases, and unfortunately people tend not to realize that.
Most of the time, you're writing program either for yourself, or your company. Internal apps (at least those I work on) rarely to never go overseas. I speak only English. So worrying about internationalization is a waste of my time. If it comes out it needs to be added later, its cheaper to do so then on the average. Now if your job is writing software thats going to be shrink wrapped and sent off around the world, you'll need it. But thats a minority of software.
If you need it, you need it. If you think there's a good chance of needing it down the road, it might be worth designign it in now. But otherwise its smarter to avoid headaches. Of course, the type of software you're writing probably highly influences this.
Gabe -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
