in reply to
Planning ahead for product name changes
The other things many programmers dread is when they're asked to perform I18N. Internationalization.
I'm astounded by how much text, usually English, typically appears in code. The most common is seldom issued error messages that are, for whatever reason, presented to the end user.
The one thing you can do is just make a look-up table for text, a sort of linguistic style sheet. This can be translated in its entirety when the time comes, instead of having to dig up every bit and piece in a panic when marketing announces they're moving into the European market. Next month.
A simple thing if you plan in advance, but very difficult if you do it in the end. Now as for the language in URLs, that's an entirely seperate argument.