Boldly Going Where Others Have Gone Before (Mimi Hills, VMWare))
•Download as PPTX, PDF•
0 likes•652 views
With Google and Microsoft publicly available MT engines what will you company’s rationale for investing in your own translation technology be? Shall we let Google and Microsoft run with it, or do we insist on our own voice, style and terminology? Machine translation technology is an innovation enabler and a force multiplier that brings the entire content universe to the audiences around the globe. Learn more about how effective use of MT opens many new services and markets.
Recommended
More Related Content
Similar to Boldly Going Where Others Have Gone Before (Mimi Hills, VMWare))
Similar to Boldly Going Where Others Have Gone Before (Mimi Hills, VMWare)) (20)
More from TAUS - The Language Data Network
More from TAUS - The Language Data Network (20)
Recently uploaded
Recently uploaded (20)
Boldly Going Where Others Have Gone Before (Mimi Hills, VMWare))
- 1. © 2014 VMware Inc. All rights reserved. Boldly Going Where Others Have Gone Before Mimi Hills Director, Product Globalization
- 2. Challenges for VMware Product G11n • The product landscape – Shifting to Agile model(s) and tool(s) – Information Experience (tech pubs) is also pressed for time – G11n is expected to be flexible and responsive • G11n business atmosphere – Technical accuracy is more important than linguistic quality (if I have to choose) • Our current human translations are not perfect • We are attempting to push quality upstream, and decrease linguistic review – Agility is more important than cost (if I have to choose) – Automation is key; no more hands-on – Bonus: a cooperative IX (tech pubs) team, using Acrolinx Confidential 2
- 3. How MT fits in • Boldly going where others have gone before – Learning from the lessons of those who started ten years ago (and earlier) • Working with Corporate Globalization and learning from each other • Start with docs from one BU and two languages, roll out more languages, more BU docs – Train vendors’ new resources on our products • Will do software strings eventually – UX is working to unify interfaces – Others have had good results with short strings – Must I continue to justify this decision? • We will provide our tools to other teams who are eager to try MT – Reverse translation too Confidential 3
Editor's Notes
- The product landscape is shifting to Agile Products available in traditional model (download) and increasingly in the cloud (Saas) Groups are using different models, and often different tools There are some to centralize tools but there’s still some choice Even Agile products tend to have a waterfall-type end game Information Experience is pressed for time Good cooperation—direction connection between CMS and WorldServer Product cycle drives late docs cycle G11n is expected to be flexible and responsive Still constant budget pressure Work across all teams, tools, processes Stick to sim ship for software, and whenever possible for docs
- I thank my trusted colleagues in other companies who’ve gone before me Working with Corp G11n—saving money too; even with dif instances we share our resources/asset have added a shared WorldServer support model Start with docs from one BU and two languages, roll out more languages, more BU docs we also get one-off requests, like slides for presentations, or slides that have come in from other companies Train vendors’ new resources on our products new because they must be post-editors not translators (some overlap) We’ve invested a lot in the technical education for our vendors (QE inc. product i18n/l10n testing as well as l10n We will provide our tools to other teams who are eager to try MT Between Corp G11n and us, will find ways to make this available across corp reverse MT for messages, surveys, etc.