Loco is a translation management tool with a staggering array of features, and a very reasonable free plan. This series of guides will cover the basics of using Loco, continuing with Part 2: Collaborating with others, covering comments, roles, and change history.
These articles are not sponsored!
Most commercial projects will end up with at least a few developers, a project manager or two, and various translators. The project used for this article currently has a total of 18 users in a mixture of countries and roles.
Your team is accessed via the “users” icon in the top right, and will show the roles of all team members, as well as precisely which permissions they have been given.
Clicking a team member will let you view some basic information such as locale and last login. Additionally, if your account has the “Manage project permissions” permission you can modify that user’s access to Loco, covered further in the next section.
Adding a new user requires the “Add new project members” permission, and is accessed via the “Invite new team member” button. Existing users in other projects can be added, or an email address and name (optional) can be submitted.
After these details have been entered, the user’s role must be picked. If on the free plan, only Translator (edit existing strings for one or more languages) can be selected. If on a paid plan, an existing project role can be selected (by default Administrator, Developer, or Project Manager), or custom roles can be created. More info on custom roles is available on the Loco site.
Once the user has been invited, they will receive an invitation email inviting them to create an account and gain access to the project. Note that users will only have a profile picture if they have logged in using a third party login (Facebook, Twitter, GitHub).
All strings can be commented on, and users can be tagged to ensure they are notified of the comment. This extra opportunity to interact with the other users provides an excellent way for translators to directly request clarification from the developers who originally added a string.
Free plans can view previous and current translations, but paid plans have a full history of all changes. The comparison selector will be familiar to any wikipedia editors, and provides information on the user, action, and time of action.
Selecting two revisions will compare any differences between the strings, with the option to view the difference horizontally or vertically, and revert an earlier change.
Notifications are by default received for all languages on all projects, and provide updates on new strings, provisional strings, and completed strings. Additionally, by default Loco will email you regularly with changes, this can be turned off via the notification settings though.
Overall, Loco’s collaboration functionality goes above and beyond similar offerings, and the string history ensures the source of any unexpected text can easily be tracked down. Additionally, clarifying translations and adding additional users is very straightforward. Considering only a single user needs to pay for the paid plans, and unlimited extra users can be added, the plans are likely to be worth it for most companies for the custom roles / full string history alone! A detailed comparison of the plans is available in Part 1.