{"id":1515,"date":"2020-06-22T14:49:48","date_gmt":"2020-06-22T14:49:48","guid":{"rendered":"https:\/\/www.asling.org\/tc37\/?page_id=1515"},"modified":"2020-06-24T10:26:20","modified_gmt":"2020-06-24T10:26:20","slug":"kshitij-gupta","status":"publish","type":"page","link":"https:\/\/www.asling.org\/tc37\/?page_id=1515","title":{"rendered":"Kshitij Gupta"},"content":{"rendered":"\n\n\n
\"\"<\/p>\n

Kshitij Gupta<\/strong> works with Adobe Systems in the role of Computer Scientist for globalization team. During his tenure of eight years at Adobe, he has led the translation technology team for the development of tools and workflows to constantly make globalization process efficient and robust.<\/p>\n

Kshitij is a regular speaker at Adobe in-house technology talks and delivered a well-received hands-on tutorial at ‘Adobe Tech Summit’. His paper on \u201cAttacking Globalized Software \u2013 and preventing it!\u201d was selected for the Unicode conference IUC-36.<\/p>\n

He also presented a session on \u201cLocalization, the efficient way to do it!\u201d at TLC 2014.<\/p>\n

 <\/td>\n

\n

Kshitij Gupta<\/span><\/strong><\/h2>\n

will present<\/span><\/p>\n

Going global? Let\u2019s measure your product for World-readiness!<\/h3>\n

 <\/p>\n

Abstract<\/span><\/h3>\n

Is your product ready for the global audience? Is string translation the only requirement you would need to cater to when you plan to go global? How would you efficiently measure your product\u2019s world-readiness? What all parameters should you measure your product on, before planning go-to market for global audience?<\/p>\n

Web\/mobile applications are becoming more prevalent and world-readiness goals need to change accordingly. Software applications now have faster iterations and quick releases. Localization of a product in short cycles at times is a challenge in itself; in absence of an appropriate mechanism to measure the scoring mechanism, focusing on improvements in localization aspects is next to impossible.<\/p>\n

Just 38% of the world population speak English; for the rest 78%, the software requires more than just string translation. Such requirements include, but are not limited to, locale awareness in terms of calendar inputs, collation capabilities, currencies, measurement units; localizability in terms of UI auto layout, resource externalization etc.; multi lingual architecture and multi-lingual text support.<\/p>\n

\u201cIf you can\u2019t measure it, you can\u2019t improve it\u201d. One needs the ability to measure product\u2019s world-readiness to set improvement goals and to evaluate feasibility for go-to\u2013market for a geography. At Adobe, we developed a framework to measure Adobe products on World-readiness score to help manage and plan global market feasibility better. The framework categorizes all globalization parameters into meaningful verticals, assigns relative weights and provides guidelines on expected behavior, testing procedures and implementation basics. On basis of collective score for a product, its globalization goals for the next release are set.<\/p>\n

In the session, we would like to discuss this framework with audience at length, discussion in detail, for multiple platforms, the expected behaviors, examples, relative importance of such parameters and the challenges encountered while resolving respective globalization issues and how the framework enables one to rightly grade the products on world-readiness and set improvement goals. Along with discussion, we would have a live hands-on score evaluation of a sample product using the mentioned framework.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Kshitij Gupta works with Adobe Systems in the role of Computer Scientist for globalization team. During his tenure of eight years at Adobe, he has led the translation technology team for the development of tools and workflows to constantly make globalization process efficient and robust. Kshitij is a regular speaker at Adobe in-house technology talks … Read more<\/a><\/p>\n","protected":false},"author":6,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"generate_page_header":"","footnotes":""},"class_list":["post-1515","page","type-page","status-publish"],"_links":{"self":[{"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=\/wp\/v2\/pages\/1515","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1515"}],"version-history":[{"count":0,"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=\/wp\/v2\/pages\/1515\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.asling.org\/tc37\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}