"Introduction to Internationalization (I18n)" by Adam Asnes, President & CEO of Lingoport (lingoport.com), a software internationalization (i18n) tools and consulting company.

1. Introduction to Internationalization Reaching worldwide markets with a single code base Presented by: Adam Asnes Lingoport, Inc.

3. Key Internationalization (i18n) Concepts

4. Business Cases

5. Approaching Globalization

6. Architecture and Code Review

7. Scanning code for issues with Globalyzer

8. Building a plan

9. Ongoing Processes

12. Common abbreviation is i18n (i + 18 letters + n)‏

15. I18n as part of development process

16. Lower Overall Cost as End Result

18. I18n Needs – Biz vs. Tech Our Software must be in Japanese, French, German, Chinese, and Spanish by November Engineering thinks about… Multi-tiered web application? Complex Interface? Database components? Embedded Strings? Locale aware application? Can it manage multiple data formats? I18n testing plan? Tactics to get it done

19. Sample Internationalization Technical Issues

20. Example: Hard-Coded English Text 1 million lines of source code Typically Found: At least 40,000 Embedded Strings which cannot be efficiently translated String orderStatus = “Your order has been processed. A confirmation e-mail will be sent to you shortly.”;

21. 11 String Concatenation Avoid Concatenation Combining two or more text strings at runtime to form a single string What order do these appear at runtime? Are they switched around? Do they combine with other strings that aren’t here? fileActions = {1} file(s) successfulAction = successfully {2} locationAction = to {3}

23. A set of characters used to support a given language or series of languages

24. Character encoding

27. I18n Architectural Challenge – what’s not in the code Marketing Requirements Locale behavior Database Character encoding support Application Code e.g. Java, C++, VB U/I e.g. JSP, ASP, ASPX 3rd Party Products Business Logic Platforms, Browser Support Requirements

29. Character encodings

30. Strings

31. Externalization

32. Concatenation

33. Display/Layout

34. Date/time handling

35. Number handling

36. Currency handling

37. Sorting

38. Searching

39. Encoding conversions

40. Locale-specific functions

41. Address formats

42. Telephone formats

43. Page layout

44. Fonts and attributes

45. Images, icons, colors

46. Bi-directional support?

47. Reporting, workflow

48. Database enabling

50. en_US = English (US)‏

51. en_GB = English (UK)‏

52. Combines language and territorial conventions for spelling, formatting, etc.

53. en_US = "color," mm/dd/yyyy, $1,234.56

54. en_GB = "colour," dd/mm/yyyy, £1.234,56

58. Large amount of code

59. Change in requirements

60. Change in architecture

61. Change in development practices

63. Market Requirements Analysis

64. Architectural Requirements Analysis

65. Code Review

66. I18n Design

67. I18n Implementation

68. Testing

69. And beyond…

70. Localization

72. Embedded strings

73. Unsafe methods/functions

74. Image references

75. Unsafe programming constructs (ex: regular expressions)‏

76. How to Identify

77. “Brute force” iterations

78. Engineers search for and resolve known issues

79. Globalyzer-assisted review

80. An I18n code analysis tool is employed to examine source code for a large range of potential and known issues

83. 1 Part Code Metrics

86. Pseudo-localization

87. A “pseudo-locale” is created and implemented with “pseudo-translated” content

89. String-length expansion issues

92. Paradigm shift: not US-centric!

93. I18n Coding Standards

94. Quality Assurance

95. I18n software lifecycle tools: Globalyzer

96. Avoid code forks

97. New features with international focus to launch in ALL locales

99. Automated i18n checking

100. Create i18n Standards