• Document: Globalization and Localization
  • Size: 329.12 KB
  • Uploaded: 2018-11-28 06:29:38
  • Status: Successfully converted

Some snippets from your converted document:

Globalization and Localization Presented by Paul Johnson Developer Division Microsoft Corporation Agenda • Part I – The Basics – Background – Defining the terms – Basic approaches to localization of web sites • Part II – ASP.NET example – ASP.NET 2.0 Globalization features – Globalization examples • Q&A Part I The Basics Some Definitions What is Internationalization? • Internationalization (I18N) – I18N - end to end product development process -- adaptable to regional users needs. – I18N - two discreet, highly interrelated activities: • World Readiness • Localization (L10N) Where’s Globalization? • World Readiness has two components – Globalization (G11N) – Localizability • Development & Design’s responsibilty – The earlier, the better! The High-level View Internationalization World- World-Readiness Localization Globalization Localizability Development & Design’s responsibility What do they mean? • Globalization: Developing program core with features and code design not solely based on single language or locale. • Localizability: Software code designed -- base code + resources Result: Program can be localized into different languages without any changes to base code. • Localization: Adapting applications for specific markets, content translation, feature customization, independent of compiled source. Globalization Example Locale/Culture • Language and cultural environment • International Standards Organization (ISO) Conventions – Language Code: ISO 639-1 (i.e., en, fr, es) – Country Code: ISO 3166 (i.e., CA, EC) – Together, they identify culture (i.e., en-US) – See RFC 3066 – Tags for identifying languages • http://tools.ietf.org/html/rfc3066 • Custom cultures are sometimes necessary Storing Localized Content • Deployment architecture affected by location of localized content – Resources, file system, database, external applications • Choices influenced by application type – Microsoft Windows versus Web • And by business requirements – Frequency of culture translations – Ease of translation process – Frequency of application maintenance What to Localize for Web Apps? • Static (hard-coded) application content – Menu/control captions, Web content, XML • Dynamic application content – Database, XML, other • Graphical content • Filenames, connection strings, queries Duplicate Site Content Web Application Resources GlobalWeb \bin Global.asax GlobalWeb.dll Web.config page and user control content Database Content logo.gif Products Duplicate Site Content Web Application Resources GlobalWeb \bin Global.asax GlobalWeb.dll Web.config translated page and page user control and \en- en-CA content user control content Database Content logo.gif logo.en- logo.en-CA.gif logo.es.gif \es Products Products_en- Products_en-CA Products_es Single Content Base Web Application Resources Satellite Assemblies GlobalWeb \bin \en GlobalWeb.en.dll Global.asax GlobalWeb.dll resources Web.config resources \en- en-CA GlobalWeb.en-

Recently converted files (publicly available):