We use the IBM ICU library for our product and it handles the vast majority of the issues presented in the article. There is no reason for me to be writing the code to handle the thousands of permutations of language, country, and culture when someone else has already done the heavy lifting here. ICU solves problems such as: sorting, number representation, etc.
The other problems should be things unrelated to Unicode - things your product / business already need.
1)Pick a target market - If you haven't picked a target market worrying about using Unicode to support some languages is putting the cart before the horse.
2)Get a translator(s) that know what they are doing - You already needed a translator - now you need to pick one competent enough to know the difference between Mexican Spanish and the Spanish spoken in Spain.
3) Write software that can switch look and feel on the fly during run time - This has already be done and should be a good philosophy for companies writing GUI intensive applications anyway.
Really - The correct sentence should be, "Just use Unicode, with your pre-existing good business practices."