{"id":59826,"date":"2019-02-05T02:04:22","date_gmt":"2019-02-05T09:04:22","guid":{"rendered":"http:\/\/www.taterboy.com\/blog\/2019\/02\/supporting-localization\/"},"modified":"2019-02-05T02:04:22","modified_gmt":"2019-02-05T09:04:22","slug":"supporting-localization","status":"publish","type":"post","link":"https:\/\/www.taterboy.com\/blog\/2019\/02\/supporting-localization\/","title":{"rendered":"Supporting Localization"},"content":{"rendered":"

By Jonathan Walter<\/a><\/p>\n

Users want to work in familiar languages and environments, so companies that build and sell enterprise products to customers from different cultures and in different locales must support these expectations. Doing so requires localization<\/em>—adapting documents or products to ensure they’re culturally appropriate. However, product teams often overlook this requirement or put off localization until late in the development cycle.<\/p>\n

Even when localization is a formal requirement, a product team that is battling a tight deadline or budget constraints may choose to skip localization or defer it until a later release. Their localization effort languishes in the team’s growing pile of UX debt<\/a>, remaining unaddressed until a senior executive receives an angry phone call from a customer, complaining about the product’s subpar experience in their native language or environment.<\/p>\n

How can you, as a UX professional, support localization, help reduce the odds that your product might alienate customers, and avoid contributing to your team’s UX debt? In this column, I’ll provide a localization expert’s perspective on this topic, then describe some practical ways in which you can design user interfaces to better support localization. Read More<\/a><\/p>\n

Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"

By Jonathan Walter Users want to work in familiar languages and environments, so companies that build and sell enterprise products to customers from different cultures and in different locales must support these expectations. Doing so requires localization—adapting documents or products to ensure they’re culturally appropriate. However, product teams often overlook this requirement or put off… Read the full article…<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[371],"tags":[],"class_list":["post-59826","post","type-post","status-publish","format-standard","hentry","category-user-experience"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t