en:postprocessing:contribute
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:postprocessing:contribute [2019/01/07 19:37] – [Quality control] thore | en:postprocessing:contribute [2022/10/09 14:14] (current) – thore | ||
---|---|---|---|
Line 32: | Line 32: | ||
* **We:** Fill the etherpad with the auto transcript | * **We:** Fill the etherpad with the auto transcript | ||
* **You:** Use for example [[https:// | * **You:** Use for example [[https:// | ||
- | * **You:** Click the " | + | * **You:** Click the " |
* **We:** Format and auto time the transcript | * **We:** Format and auto time the transcript | ||
* **We:** Upload the transcript with the timestamps to amara | * **We:** Upload the transcript with the timestamps to amara | ||
Line 42: | Line 42: | ||
The subtitles created live can rarely be used to create subtitle-tracks. Most of the time their quality is too poor as that they would save you any time. Creating clean recording-quality subtitles from scratch is usually faster. | The subtitles created live can rarely be used to create subtitle-tracks. Most of the time their quality is too poor as that they would save you any time. Creating clean recording-quality subtitles from scratch is usually faster. | ||
- | Should there be a Talk where that's not the case and you remember a especially good live subtitle please write a mail to subtitles -!-at-!- | + | Should there be a Talk where that's not the case and you remember a especially good live subtitle please write a mail to subtitles -!-at-!- |
Our quality requirements towards subtitles for recordings are different to those for live-subtitles. Unlike it is common in other places, we want our subtitles to be as accurate and close as possible to what has actually been said. Besides fillers like " | Our quality requirements towards subtitles for recordings are different to those for live-subtitles. Unlike it is common in other places, we want our subtitles to be as accurate and close as possible to what has actually been said. Besides fillers like " | ||
Line 84: | Line 84: | ||
==== (Auto-)Timing ==== | ==== (Auto-)Timing ==== | ||
- | When the transcript of a video is done the transcript needs to be timed accourding | + | When the transcript of a video is done the transcript needs to be timed according |
<WRAP round box info> | <WRAP round box info> | ||
Line 101: | Line 101: | ||
=== Quality control === | === Quality control === | ||
- | After auto-timing, | + | After auto-timing, |
Optimally that's done by a different person than the one who transcribed the talk. You might find someone to do QC on your subtitles in the IRC.\\ | Optimally that's done by a different person than the one who transcribed the talk. You might find someone to do QC on your subtitles in the IRC.\\ | ||
+ | \\ | ||
However, if you can't find anyone it's still better to do it yourself than to not publish the work. | However, if you can't find anyone it's still better to do it yourself than to not publish the work. | ||
Most important is to check for (auto-)timing errors, and to adjust timing if necessary.\\ | Most important is to check for (auto-)timing errors, and to adjust timing if necessary.\\ | ||
That is again done in Amara. | That is again done in Amara. | ||
+ | |||
+ | At this point in time most subtitle blocks are formatted in double lines with a maximum length of 42 characters each. Please do not change this, this is done this way intentionally. It improves readability by creating blocks which are shown for a as long as possible period of time, especially in fast tech talks. | ||
As during the transcription process, please save your draft regularly and note the timecode of how far you got in the subtitles interface. | As during the transcription process, please save your draft regularly and note the timecode of how far you got in the subtitles interface. |
en/postprocessing/contribute.1546886239.txt.gz · Last modified: 2020/09/19 22:03 (external edit)