2. Enter into new markets more easily Lower cost and time for development and translation Increase customer satisfaction and adoption Avoid costly mistakes (and potential lawsuits!) The boss said you had no choice

3. Everyone plays a part in international quality Designers need to be “thinking international” Developers need to be “thinking international” There is no substitute for a collaborative and knowledgeable team “OK” In North America… In Brazil… “Not OK” In France… “Zero” or “Worthless”“Money” In Japan, Korea & China…

4. Globalization The process of developing a program core whose features and code design are not solely based on a single language or locale. Localizability The design of the software code base and resources such that a program can be localized into different language editions without any changes to the source code. Localization Translating a product for a specific market Marketization Customizing a product for a specific market

5. Requirements (Start Here) 1)Foo 2)Bar 3)Intl! Code Release Design Test

6. Code Design UI Freeze Localization Acceptance Tests

8. English GermanRussia n Japanes e Thai One bad design here… …needs to be fixed n number of times Design UI and software code so a program can be localized into different languages without any changes to the source code Why is this important: One badly designed element costs you multiple times

9. No code changes should be made for localization – so design for all cultures Design UI with string expansion in mind (30%) Avoid overcrowding dialogs and forms Developers - use AutoLayout where possible Never, ever do something like this: BAD GOOD

10. Use clear and consistent terminology everywhere Avoid highly technical sentences and colloquial phrases “You are dangerously low on disk space.” “Unable to fork daemon.” Minimize the use of acronyms, abbreviations, string decorations and string concatenations “The DHCP server issued a NACK to the client.”

11. ExamplePreferred Avoid text embedded in images Avoid gender and ethnic stereotypes Avoid culture-specific examples Avoid body parts and gestures

12. http://www.microsoft.com/virtualearth/platform/

14. Technical content follows

15. Numbers: 9,000.00 is 9.000,00 in Germany Currency: Symbol placement: 9.000,00 DM in Germany Negative Numbers: kr-127,54 in Denmark Large numbers: 123,456,789.00 is 12,34,56,789.00 in Hindi 123'456'789.00 - in German (Liechtenstein) Sort order: Germanä comes after a Swedishä comes after z.NET Framework let you worry less about this stuff. http://msdn2.microsoft.com/en-us/library/1021kkz0.aspx

16. using System.Threading; using System.Globalization; int myInt = 100; Console.WriteLine(myInt.ToString("C", Thread.CurrentThread.CurrentCulture)); If the culture is set to "fr-FR", output is: 100,00 If the culture is set to "en-US", output is: $100.00 If the culture is set to "fr-FR", output is: 100,00 If the culture is set to "en-US", output is: $100.00

17. Unicode needs encoding to work UTF-8 – use for web apps and interoperability UTF-16 – use for.NET WinForm application Email is an exception Should continue to use non-Unicode encoding types, such as ISO 8859 series, as the default encoding type for the out-going messages for legacy reasons For tons more information on Unicode http://www.microsoft.com/globaldev/getwr/step s/wrg_unicode.mspx

18. Non-English input methods National standard keyboards IME (Input Method Editor) Use.NET edit controls wherever possible

20. Make sure all fonts cover one or more character sets. Remember punctuation marks, numbers, uppercase and lowercase letters etc. All fonts shipped in Windows are Unicode ready. Font size should be no smaller than 9 points or allow font size change Web Developers -- avoid placing font attribute values into inline styles. Use CSS in which font attributes and style are defined in separate files, at least one for each supported culture. Read more at: http://www.microsoft.com/globaldev/getwr/steps/WRG_font.mspx

21. Use satellite assemblies! By isolating resource elements in separate language specific binaries, you can: Display your application UI in the language of the OS Set the UI language per user Allow on-the-fly UI language switching Add/remove language modules as needed Read about.NET resource handling and satellite assemblies: http://msdn2.microsoft.com/en-us/library/f45fce5x.aspx

23. Knowledgeable designers and developers World ready software is a team effort – collaborate! Set up an international best practices document for your org Train your new hires Don’t re-invent the wheel Use all the tools and best practices you can get your hands on.NET Framework significantly reduces effort When in doubt, ask Dr. International http://www.microsoft.com/globaldev/drintl/askdrintl.mspx

24. You Are Not World-Ready If... http://www.microsoft.com/globaldev/getWR/nwr/notworldready.mspx Ask Dr. International http://www.microsoft.com/globaldev/drintl/askdrintl.mspx Globalizing and Localizing Applications using the.NET Framework http://msdn2.microsoft.com/en-us/library/1021kkz0.aspx Localization Quickstart For Web Application http://quickstarts.asp.net/QuickStartv20/aspnet/doc/localization/localization.aspx Visual Studio AutoLayout Examples http://blogs.msdn.com/permanenttan/archive/2006/03.aspxhttp://blogs.msdn.com/jpricket/archive/2006/04/05/569280.aspx Microsoft Virtual Earth Platform http://www.microsoft.com/virtualearth/platform/Unicodehttp://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspxFontshttp://www.microsoft.com/globaldev/getwr/steps/WRG_font.mspx Resources and Satellite Assemblies http://msdn2.microsoft.com/en-us/library/f45fce5x.aspx

25. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.