1 / 22

Winning Global Market Opportunities

Winning Global Market Opportunities. Data-driven Localization strategy . Data Driven Decisions. Localize and internationalize. Why. Why G11N? Economy and IT Spending grow faster in APJ, Middle East & Africa, Latin America than in the US. % Increase in GDP size between 2013 and 2017. 29%.

donaldtilley
Télécharger la présentation

Winning Global Market Opportunities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Winning Global Market Opportunities Data-driven Localization strategy 

  2. Data Driven Decisions

  3. Localize and internationalize Why

  4. Why G11N? Economy and IT Spending grow faster in APJ, Middle East & Africa, Latin America than in the US. % Increase in GDP size between 2013 and 2017 29% 26% 20% India 12% 9% Thailand Saudi Arabia Brazil China Turkey South Africa Russia Malaysia North America Europe LATAM Hong Kong MEA APJ Australia Mexico UK Canada US France Japan Germany

  5. Revenue Outside the US is Greater than the U.S. Revenue outside the US

  6. Top 11 Countries by Market Opportunity

  7. Top 11 Languages FY17 Market Opportunity

  8. Why Globalization? Losing Millions of dollars by Missing out on opportunities! • 7 Sample products that were NOT enabled for global markets • Lost market opportunity • Engineering efforts to fix $4,995,000 + $667,000 $5,662,000 • Total Loss for a single year $185,900 • Cost to design right - only 3% of the Total Loss. Projected 3 year cost = $17M! for 7 products alone

  9. Globalization: Cost of Defects 1,198 1,025 835 Customer found defects cost 50 times more

  10. Without L10N: Users utilize less than 5% of features

  11. Global Readiness how

  12. Global Readiness Scorecard

  13. Design Design • Is Unicode used for I/O with file-system and network communications for application text data? • Have you verified that your libraries or APIs support Unicode in their interfaces? • Are Unicode data types used in database table columns? • Have the patching and upgrade scenarios for localized versions of a product been confirmed and documented in design specifications? • Are you using identifiers instead of string values in application logic? • Have you confirmed that your application's localizability model conforms to I18N guidelines? Sample

  14. Text Processing • Is Unicode used to process text strings throughout the code, including input, output and display? • Are users able to search for arbitrary Unicode character strings where applicable? • Text Processing: For Windows software, are the Unicode versions of API calls used? • Regional Support • Is display of any times, dates, numbers and calendars (including date-pickers) sensitive to the client locale? • Did you use a locale-neutral date/time format (ISO 8601) and UTC time zone for date/time strings used in application logic and serialization? • Localizability • Are text strings presented so there is no string concatenation in the code and UI controls? • Are buffer lengths are sufficient for localized string expansion, and can the UI correctly handle localized UI string expansion, how about fallback? • Are all translatable strings extracted to external resource files? • Are standard resource file formats used throughout the product? • Do all strings with placeholder variables allow those variables to be reordered in support of localization? • Is there correct language fallback behavior as per user's preferred language or locale? Coding Sample

  15. Install • Product installation or deployment and end-to-end functionality works properly with localized Operating systems and multiple locales? • Text Processing • Application supports Unicode supplementary characters? • Multilingual data is sorted using Unicode Collation Algorithm? • Search, Filter and Find functionality works properly with non-ASCII characters? • Multi-lingual data processing functionality using arbitrary valid Unicode characters in import/export data, paths, open/save locations, file names?   • Regional Support • Non-Gregorian calendars are supported?  • Text comparison and sorting is done according to user locale setting? • The product supports regional date/time, number and digit, addresses and currency formats according to regional settings? • The First day of the week is defined according to the selected calendar based on Locale/Culture Info? • Localizability • Have you tested using a pseudo-localized build?  Sample Test

  16. Product Global Readiness

  17. Language, Market, Scope What

  18. Product Localization: Decision Criteria

  19. Criteria – Definition & Ranges

  20. Score Ranking Sample Sample

  21. Data Driven Globalization: Re-Cap

  22. jenny.kang@veritas.com Q&A

More Related