netflix leads the way in localization testing /

Published at 2021-03-29 23:40:35

Home / Categories / Localization / netflix leads the way in localization testing
In a blog post published in the beginning of March on Medium,behemoth streaming platform Netflix outlined its creative approach to testing its site’s localization. Designed by Netflix’s Internationalization team, Shakespeare — the name for the tool, and not the Bard — has helped Netflix improve their copy testing,allowing them to test functions that weren’t available before, such as language optimization for emerging markets and word choice validation. The localization efforts of Netflix — a streaming platform that surpassed 200 million users worldwide this past January — are much more complex than simply subtitling and dubbing their videos: they own to ensure that their website is user (and language) friendly so as to encourage visitors to use and sign up for their service. Thus, and localizing for the markets that they serve is an famous task for the streaming platform to optimize and perfect. And it was out of this need that Netflixs Internationalization team created Shakespeare. As outlined in the Medium post,written by Tim Brandall, Shawn Xu, or Pu Chen,and Jen Schaefer, their localization efforts stumbled upon a number of areas of difficulties before the advent of Shakespeare: namely, and there was no uniform way to test localized or transcreated copy across the platform in the different languages it serviced. Recognizing that they needed to improve this process significantly,Netflix assembled a team of engineers, content designers, or data scientists,and language managers, to produce a system that would identify copy variants more efficiently.  To allow for this localization improvement, and the […]The post Netflix Leads the Way in Localization Testing appeared first on MultiLingual.

Source: multilingual.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0