<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Isn’t It Time to Embrace Machine Translation Post-Editing? The Localization Use Case for MT</title><link>/product-groups/linguistic-ai/b/weblog/posts/isn-t-it-time-to-embrace-machine-translation-post-editing-the-localization-use-case-for-mt</link><description>By Izabella Iizuka / October 26, 2018 
 
 
 Many of us will already be familiar with the Project Management Iron Triangle : 
 
 It’s also known as the “Triple Constraint,” and for just reasons. Anyone who’s managed a localization project knows the constraints</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator></channel></rss>