Skip to main content

Bike Inside Trados Delivery Project

 

I grouped together with 3 other translators to simulate a Trados delivery project from beginning to end to learn about Trados's challenges and setbacks in more depth. The project included creating a SOW/work proposal based on CAT tool analysis, pseudo-translation, establishing a Style Guide, a glossary, and TMs, delivering the final language packages, and recording a video on lessons learned.

Follow along with our experiences of the creation of a Trados delivery project for localizing a short text from the website "Bike Inside" divided into 4 languages. The translation process simulates the experience of translating in a small, in-house translation team or in a small group of associated freelancers.

Introduction

WHAT IS TRANSLATION TECHNOLOGY?

Translation Technology refers to technologies that are important in management, engineering, and linguistic roles in translation and localization, including various tools that aid the process of translation and editing workflows.

As a Translation and Localization Management graduate student in the Middlebury Institute of International Studies at Monterey, the Translation and Technology course thought by Prof. Adam Wooten helped me to understand better the significance of CAT tools to create translation memories, termbases, and manage terminology, to reuse previous translations to perform quality assurance within the tool beyond the regular processes of translating and editing.

More, the course included some interesting lessons about different types of machine translations and post-editing from the perspective of a translator. As part of the course work, within the Bike Inside Trados delivery project, I grouped together with 3 other translators to simulate the workflow of a translation project from beginning to end using SDL Trados.

If you are interested in the subject of AI and MT, read my blog post here:

AI and Translation Technology

Proposal

STATEMENT OF WORK

A Statement of Work (SOW) is a document within a contract that describes the work requirements for a specific project along with its performance and design expectations.

When setting up a translation project and communicating with a potential client, it is essential to provide a short, clearly written statement about the project details that contains the expectation and requirements of the project to avoid misunderstandings. The statement of works includes the name and the description of the project, the timeline with appropriate due dates, cost, and resources (people, time, tools). Additionally, the SOW includes the outline of the phases of the translation project starting with the setup or preparation phase which demonstrates to the client that everything is ready for translation. In our case, the emphasis was to show how Trados will be used to execute the job and how it will help with the initial setup to simplify the technical and linguistic aspects of the entire project. The setup phase will be followed by the production phase which includes additional details and steps if necessary. The final phase is finalization to ensure that the translation meets all the requirements set up previously.

Finally, the SOW lists all the deliverable files and documents that were agreed upon with the client.

Because we found some errors in the source text, we suggested some edits to the client and agreed that we will include both the original and the suggested source file in the deliverables.

Ideally, the presentation of an SOW involves meeting with the client in person or - given our limitations these days with personal encounters -, an online meeting where both parties can raise questions and come to a final agreement. After the agreement, the translation process can begin.

A translation project proposal that contains the description, specifications, goals, timeline, costs, and resources, as well as the preparation, production, and finalization phases for the client.

Delivery

TRADOS DELIVERY PACKAGE

Our Trados delivery package included the following files and documents:

Deliverables:

  1. Source document (original)
  2. Source document (with proposed and accepted edits implemented into our CAT tool set up)
  3. Style Guide for Quality Assurance

Language deliverables:

  1. German: Pseudo translation (Word); Target text (translation , PDF); Translation Memory; Term Base (glossary)
  2. Hungarian: Pseudo translation (Word); Target text (translation , PDF); Translation Memory; Term Base (glossary)
  3. Italian: Pseudo translation (Word); Target text (translation , PDF); Translation Memory; Term Base (glossary)
  4. Portuguese: Pseudo translation (Word); Target text (translation , PDF); Translation Memory; Term Base (glossary)

BIKE INSIDE TRADOS DELIVERY

You can see and download the files for this project here:

Lessons Learned Video

Watch the Lessons Learned Video here:



Contact me:

Comments

Popular posts from this blog

Discussion: Managing Stakeholders

A point of view of a freelance localizer and translator Who was the stakeholder and what was their role? For this discussion, I am going to use my freelancing experiences and use my clients as stakeholders. These clients are mainly LSPs and within that, primarily need to deal with translation project managers or project coordinators. In some cases they are more on the junior side, meaning they are not involved that much in the entire project but only in the coordination between linguists, and in some cases, they are senior project managers who have more interests in the project outcome because they need to manage them from beginning to end and they also need to deal with their clients. In some cases, depending also on the client and the size of the company, the project manager can be the owner or the president of the organization at the same time. As I mainly had pleasant experiences with these stakeholders, I am going to explain how I learned to deal with them in general going into de...

Contentful Headless CMS - l10n & i18n

Exploring Contentful for Translation and Localization It seems there is a new buzzword in the website building industry: headless CMS (Content Management System). But what is exactly a headless CMS and how does it work? In this write-up, I am going to walk you through the different steps of how I explored one of the most popular headless CMSs, Contentful; how I created a simple website with it; and what approaches I took to localize the website into another language. In the end, I realized that I needed a completely different mindset on website building and localization in general. And I had a clear vision of when a headless CMS is useful and when it is recommended to use a traditional CMS, like WordPress, instead. Finally, I learned a lot about Node.js, Gatbsy.js, website deployment, and the many challenges i18n problems introduced into the subject. Part 1: Headless CMS & Contentful What is headless CMS? A headless CMS is a platform that has no default front-end system to determin...