Amara is in the process of switching to a new subtitle editor that is easy to use and also very powerful for professional work. It is currently in beta but will become the primary editor soon. Take a look below to see how it works, and what's to come!
Advantages and features that will be available in the released version.
(most features are available now!)
Help prompts for subtitling staging:
Amara Style Guidelines (configurable for Teams)
Add a new language dialog
To use the new Amara editor:
Syncing the subtitles to the video
In step 2, play the video and press the down arrow to insert the subtitle at the right moment.Syncing controls:
The right side panel indicates when all lines are complete and synced.
Once all lines are timed, and there are no blank lines, you can move to the next step by clicking Start reviewing
Click Complete when done to save the completed version of subtitles.
If you need to exit the editor before subtitles are completed:
Adding a new translation:
• Download the subtitle version that you want to use for offline work
• When editing be sure your edit confirm to the standard for the subtitle format type you are using.
ex: for srt format subtitles, italics are denoted as <i> italics </i> and you must properly close the tag. Unclosed tags won’t be parsed properly. Lines with * italics * will remain unchanged.
• When you have completed the editing, upload the subtitles via the amara ui.
If you have removed lines from the translation choose
in the upload dialog. Otherwise your subtitle timings will be offset by the blank lines.
After uploading a new version carefully check your subtitles for any errors before continuing. It is much simpler to correct errors before further edits are made and can prevent you from losing work.
Regarding going back to typing mode:
It's not so obvious in the UI yet. But if you hide the timeline - you are effectively back into Typing mode, where hitting enter will add a new line, and using the up / down arrow keys will not affect syncing. Show timeline, to go back into syncing mode.
Happy to see changes being rolled out.
A. The new editor seems easier to use now, though navigation commands still don't work for me (Mac OS X, Firefox 30.0 and Swiss French keyboard) except tab for play/pause that does work.
-> Could you fix these navigation commands, please?
Created a ticket here: https://github.com/pculture/unisubs/issues/1069
B. it remains easy to goof the correspondence with the original subtitles when using it for translation by skipping a line. I did when continuing the English subs of Naufrages en Méditerranée, à qui la faute? (...) yesterday, though I fortunately noticed the error before saving.
-> What we really need is the possibility not only to unlock the original subtitles, but to relock them accurately after making them face the corresponding translated subs, especially for long videos (this one is only 15 minutes).
https://github.com/pculture/unisubs/issues/950 - is one of the top new editor tickets we are working on.
C. I had to switch to the new editor for continuing the English translation (or continue the translation from the video with the legacy editor, but that's a pain in the neck) because I had made some minor corrections in the original French subs of the same video with the legacy editor, even though the number of subs remained the same (I only adjusted some timings and corrected one transcription and the spelling of some names). This means that the Italian translator will be in the same situation should s/he try to update the translation according to the changes I made in the original.
-> Could you please specify what changes to the original subtitles should be avoided lest they prevent other people to continue translating from them with the legacy editor, which remains more user-friendly?
And change to the timing (adding or removing lines, changing the timing, or uploading a new version) of the source language will cause the translations to be 'forked' and therefore require the new editor.
We are working on this ticket that should simplify updating the timings on the translation:
Claude - that's a link to an internal working doc mainly as a reference history for the developers working on the ticket. The actual changes we are working on are in the tickets that are all public on gh.