The workflow is a series of steps. Any step can be hidden and new steps can be added. The Admin user designs the workflow for the team. Templates of workflows for common solutions are provided. All projects on the team use the same workflow. The step names can be changed and localizations are provided. Each step is associated with a particular tool. Multiple steps can use the same tool and of course not all tools need to be used. The user is guided through the steps but can go back to repeat any steps or adjust any of the previous content. (Watch a demo.)
When a passage makes reference to a particular cultural topic, it may be helpful for those recording a translation of the passage to have a background description of this topic. This description can be provided as an audio resource or as a text / display oriented resource. Other resources could be translations of the same passage in various languages that are known to the translation team. (Watch a demo.)
Threaded discussions are very similar to commenting tools provided by Word or Docs. They allow the selection of a segment of the recording and the creation of a discussion around it. The discussion can have contributions from team members. These contributions can be audio or text. The entire discussion can be assigned to a person or role and can be resolved when finished. (Watch a demo.)
Community checking for orality projects is often done by playing the audio of the passages in the section for an “uninitiated” speaker of the language who is then asked to retell the section in their own words. As the retelling and translation are compared, observations can be recorded in discussions about things that were added or things that were left out. Another tact is to play an excerpt and ask questions about it and record the answers. The retellings or answers can be transcribed. (Watch a demo.)
These tools allow the user to listen to the passage and then record their back translation in a language understood by the consultant. This can be done for the entire passage or the passage can be broken into phrase segments and each segment can be back translated. These back translations can also be transcribed and sent to a Paratext back translation project. (Watch a demo.)
Paratext integration has been improved so that if a project has a registered back translation project, the program will choose the corresponding project or back translation project depending on what content is being synced. As in the past, the language code is very important for linking SIL Transcriber projects with the corresponding Paratext projects, either locally or in the cloud.