Going international - using Unicode's CLDR Project to localise your software

When serving users in different markets around the world, gettext gets you 80% of the way there, by making it easier for you to extract strings from your app, translate them offline and then compile the translated string into your code so that they can be shown dynamically, based on the user's locale.Some strings are not static, so with gettext, you can add placeholders to your string, and feed the dynamic parts in at runtime, as variables. But what if the variable itself needed to be translated? When the variable is something like a date, or a currency or a phone number, users in different locales would expect them to be displayed in different ways.You could fix this the hard way, with if-statements... or you could use ex_cldr to fix it for you.In this talk I will

• show how to get set up with gettext, ex_cldr and a few of the related packages
• work through a few examples of where this might be useful
• point-out some common pitfalls & limitations.