Wenting in localization

Introduction

Translation Management Systems are an essential part of localization technologies. In this class, I learned all the basics of  WorldServer, including setting up project workflows, organizing workgroups and leveraging translation memories. It also equipped me with valuable skills to work with other TMS in the industry such as XTRF and Transifex.

Group Project

In this portfolio you will see a demo localization project I worked on. My group and I localized Geico’s history page using Worldserver. I worked as a Project Manager and oversaw the successful completion of this project. I also worked as a localization engineer as I preped the files, set up all the workflow, initiated the project in WS and generated the final deliverables.

You can download all the project files following this link. It includes the following documents:

1. A project proposal detailing the scope of the project as well as the time and resource cost
2. Project deliverables including source files, target files, and translation memory and term base files
3. A slide show of what the group has learned from the demo project

Recommendations to a better WorldServer

WorldServer by itself is now an adequately good tool – it works with the most common files types; takes advantage of TMs and TDs and leverages the cloud technology. However, I believe by implementing some of the following features, WorldServer could become a better and stronger tool:

• WYSWYG

If you want to translate using WorldServer, you use the Desktop Workbench or export the project in xliff format and translate it in a CAT tool such as Trados. Neither approach allows the translator to see the sentences in context. More often than not the PM has to send the translator the additional reference documents and web links in a separate email. The WYSWYG feature could allow the translator to work in context and thus generate better translation results.

• Better desktop and online/offline integration

WorldServer only allows you to download the translated files through the explorer tab, which requires special java configurations to run. It can become very inconvenient sometimes. I hope WorldServer could be more like Dropbox where you can edit the files locally and have them synced across the cloud automatically while having version control options. I believe it is a far more modern and user-friendly solution.

• Better and more integration with other Content Management Systems

WorldServer has some integration with the major content management systems such as Adobe Experience Manager, Drupal and WordPress. However, for less known CMS owned by companies such as Oracle, there is no existing connector between the CMS and WorldServer and all the contents have to be exported and imported manually. Such approach is prone to human mistakes and costs a lot more. WorldServer could definitely score more points if it had better integration with other CMS.

Welcome to Sites @ MIIS. This is your first post. Edit or delete it, then start blogging!