How to tackle an Approval

From OTPedia
Jump to: navigation, search

Approval is the last step that the translation or transcript go through before they are published. Approvals are done by Language Coordinators after a transcript or translation have been reviewed.

Contents

What is the job of an approver?

Approval is the last task before publishing, so the approver has to verify the quality of the translation and correct any remaining mistakes. If the transcript or translation were poorly reviewed and extensive editing is necessary, the approver should return the task back with instructions detailing what needs to be changed and how (ideally including links to helpful resources like the guide to reviewing talks).

Important: Note that when you send back a review, this may cause a crediting error where you will end up being credited for the subtitles. If this happens, please email the TED OTP team at translate@ted.com, explaining what happened, and including all the relevant info (link to the talk on Amara and on TED.com/YouTube and the names of the people who should get credited).

How to approve a task

Below, you will find instructions on what aspects may need fixing and how to fix them. Remember that if you find the transcript or translation need extensive changes, you can always send the task back, explaining what needs to be done. Hint: before sending the subtitles back, it's a good idea to make the necessary changes in the first few minutes, to show the reviewer what you mean.

Fix the reading speed

Using the new ("beta") editor, you can check the reading speed and character length of every subtitle. This tutorial explains how to use this information. Fix the reading speed by compressing/reducing text or by editing the timing. If compression doesn't work, you can extend the duration of a subtitle a little and make the following subtitle start a little later. You can also sometimes merge subtitles that together form a complete sentence or clause (put all the text into the first subtitle, delete the second subtitle and extend the duration of the first one over the gap). Don't merge subtitles if the resulting subtitle would include part of the next sentence.

Fix the line breaks and subtitle length

In languages that use Latin script, every subtitle longer than 42 characters must be broken into two lines, and no subtitle can have a total length of over 84 characters. Even if a subtitle is broken into two lines, the break may be placed in a way that splits up a linguistic whole, e.g. after an article. Fixing line breaks involves inserting line breaks into unbroken subtitles with over 42 characters and relocating the line-break if one of the lines is over 42 characters or if the current line break splits up a linguistic whole. It may sometimes be necessary to rephrase the translation a little to make breaking a subtitle in keeping with the rules possible. For more tips on line-breaking, see this guide.

Scan for translation accuracy, grammar, spelling and punctuation

Do a sweep for mistakes in meaning, grammar, punctuation and spelling. Some common types of mistakes are:

Check the title and description

Make sure that the title and description were actually translated and that the speaker's name isn't missing. When approving TEDxTalks, make sure the title structure is correct and that the description only contains a brief description of the talk (learn more here). In TED-Ed videos, make sure that the information about the author of the lesson and the animation has been translated.

How to select tasks for approval

Selecting tasks for approval may be tricky, especially if there is a long back-log of talks waiting. Here are some tips on the selection process.

Mix old tasks and new tasks

If there is a long queue of approval tasks waiting, try to mix working on some of the oldest tasks and some of the ones done recently. If you only focus on the tasks waiting the longest, new volunteers won’t get the feedback necessary not to make some mistakes in their future work. At the same time, if you only focus on the newest tasks, volunteers who have been waiting for their work to see the light of day may lose the motivation necessary to keep working on new tasks, and they may be less likely to go back and implement your suggestions if a long time has passed since they last worked on the given task.

Help people learn from your comments

Before you start, always look at the revision history and find out whose work you are approving. If you have sent back one reviewer's work several times before, and you saw them gradually improve based on your comments and actually implement your feedback, you may want to spend less time on making corrections on your own and instead send the work back with instructions. This may seem counter-intuitive, but more advanced reviewers will often enjoy improving their work armed with the knowledge gained from LCs' feedback – they can fix stuff that they simply didn't originally know was an issue. This approach can also give you more time to focus on guiding beginners by correcting more of their work.

If you can tell somebody is a beginner (e.g. it was their first review), consider making more changes than usual before sending the task back, or even fixing the mistakes on your own to provide a good model, while adding comments explaining what you did and why, and how to avoid similar mistakes in the future. The first-timer may be confused about your comments and not know how to make the necessary changes, so your model examples will help with that. Make sure to instruct the reviewer how to compare your revision with their final work.

What to put in your comments

Comments on an approval are an invaluable resource for the volunteers. Below, we have some suggestions on how to structure your feedback.

Share common comments with other LCs

You will find yourself commenting on the same thing over and over (e.g. "Please use the correct title and description standard for TEDxTalks"). It may make your work easier if you and the other LCs who work in your language share a Google Doc with templates for the most common comments. You can then copy the appropriate comment and only adapt it a little to fit the current task (e.g. by giving examples taken from the subtitles you are working on).

Give examples of mistakes

While general feedback like "don't use English punctuation rules" may be helpful, it is better to provide at least one example from the subtitles you are working on to show the other volunteers what exactly you have in mind. In addition to quoting the example, add the corrected version (e.g. "This a, subtitle" --> "This, a subtitle").

Don't get personal

Remember that you are commenting on the work, not the contributors. Try to be objective in your comments and even if somebody has left a lot of mistakes in the subtitles, don't get your frustration out on the other volunteers. Keep in mind that the Open Translation Project promotes an atmosphere of peer learning and tolerance and a lot of volunteers will simply require some time to learn. If there are serious problems with somebody's work which don't seem to be helped by your feedback, discuss teaching strategies with the other LCs.

Find something positive

Very often, you may find yourself commenting only on the issues and mistakes. But remember to also point out what worked in the subtitles. Even if you needed to fix the reading speed in every subtitle, perhaps the translator was great at expressing humor or did careful research on terminology? Or perhaps the translation was full of spelling mistakes, but totally accurate in terms of meaning? The volunteers need to know about things they should keep doing, and your positive feedback will show them the way to go.

Refer to objective standards

To help the volunteers develop an attitude where they feel empowered to research the proper rules and solutions on their own, don't just base your feedback on your authority, but add a link to an outside, reputable resource that both you and the volunteers can refer to in judging what is correct. For example, when you are telling someone a phrase that they used is ungrammatical, find a link to a resource by a language authority in your culture that explains why the given phrase is incorrect (e.g. a well-known style guide). This way, the volunteers will feel that the level of skill necessary to be good at translating and reviewing is fully accessible to them provided that they base their decisions on more careful research.

Include links to guidelines and tutorials

We have a variety of general resources on how to prepare subtitles that you can share with the OTP volunteers to help them improve their work. When making a comment about an aspect of the subtitles that you have corrected (e.g. frequent reading speed problems or incorrect formatting of the title and description), make sure to link to the appropriate subsection of the whole guide. To obtain the direct link to a subsection, click its title in the table of contents at the top of the OTPedia article and copy the full URL from your browser's address bar.

Here are the links to some of the guides on OTPedia:

  1. How to tackle a translation
  2. How to tackle a transcript
  3. How to tackle a review
  4. How to break lines
  5. Sound Subtitling Guidelines
  6. Video Tutorials

Some languages have their own translated guides. Based on the English-language resources, you can write your own guides in your language, and share them on OTPedia and in your language group.

Personal tools
Namespaces
Variants
Actions
Navigation
Languages
Toolbox