Shuttle organizes translation work into separate commits among different projects. Commits are given a priority and due date, so translators can focus their effort where it is needed most. Project managers can track the progress of commits, ensuring that localization is done on schedule.
Shuttle checks out your project's Git repository and automatically scans for localizable content and imports it into its database. Translators can begin translation of new content immediately, with no engineer intervention required. When a commit is ready to be released or deployed, Shuttle makes available a manifest of translated strings in any of a variety of formats, to easily integrate back into your project at build time.
The translator workbench is designed to make translation and review as fast and accurate as possible. Translators have access to tools such as the glossary and translation memory to help improve their accuracy and ensure a consistent voice across translators and projects.
Shuttle recognizes non-translatable substrings (such as ERb escapes and HTML character entities) and fences them out. It displays an error if translators omit or mistype fenced tokens.
Shuttle maintains typographical quality by ensuring translators use curly quotes, em-dashes, and other non-ASCII characters when appropriate.
Reviewers and administrators can contribute to a project glossary that standardizes common terminology across projects and translators. Reviewers maintain a corpus of commonly-used or jargon-like terms and phrases, and translators contribute standardized translations of these in their respective languages. These terms are presented on the workbench when appropriate.
Shuttle maintains a complete memory of every translation contributed, even if the source string is no longer present. These translations contribute to a suggestion engine to save translator time and effort and ensure a consistent voice across time. Administrators can cull bad translations from this memory.
Shuttle displays statistics to help project managers budget translation effort and track the improving speed of translators. Users can track trends in the average amount of elapsed time between when a commit is submitted for translation and when it is fully translated and review, as well as see periods of intensive translator demand, and which projects require the most translation effort.