docs.locize.com Open in urlscan Pro
2606:4700::6812:191  Public Scan

Submitted URL: http://docs.locize.com/using-locize-as-translator
Effective URL: https://docs.locize.com/using-locize-as-translator
Submission: On May 13 via api from IE — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

locize documentation

Help CenterBlogSign inlocize.com

Search…
Introduction
Using locize
What's inside?

The different views

Checks/Issues
Using locize as a translator
Integration
Getting started

Instrumenting your code
API
Webhook
CLI
I18n Formats
File Formats
Guides / Tips & Tricks
Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators

Migrating an i18next project
Migrating from ...

More
InContext Editor

Figma Plugin
Versioning
Namespaces
Caching

Backend Fallback
Latency Optimization – Tips for Optimal Performance
Notifications
2-factor authentication

Convince Your Boss Letter
General questions

Powered By GitBook
Using locize as a translator


Your journey using locize might start with a short invitation email you received
asking you to sign up for the service. Hopefully, the person inviting you
already gave you some context information about your task. After following the
invitation link in the email and going through the registration process you will
find yourself on the dashboard which contains all projects you got access to.

Finding yourself here the first time there will be only one project so click
that one. You will now find yourself in the "ControlCenter" of the project.
Depending on your access rights that page will lead to many administrations
settings but most interesting for you is the section "Start to translate":

If the language you translate to is not yet selected toggle that to the correct
language. As you can see the file "translation" is not completely translated.
You now have the option to use two different views for translations using the
buttons on the right.

THE GLOBAL VIEW

Acts as an overview and will highlight changes made.

You can learn more about that view here. As the global view is less targeted on
the translation workflow we will follow the button to the focus view.

THE FOCUS VIEW

This view is primarily created for translators focusing on one text segment at a
time using additional information at hand (machine translations, translation
memory, context information,...).

GETTING THE JOB DONE

As you can see above - in our case - there are only 4 segments that need our
attention and are not yet translated. Your list might be a lot larger so the
best will be set a filter only showing segments that are untranslated:

Which reduces the list to the untranslated segments:

You now can either pick a translation provided by the machine translations and
post edit the content or type the translation into the input field.
To navigate to the next segment either click it using the mouse or use the key
bindings:

Depending on being on windows or mac the bindings can be different so better
check them on your system. Having gone through the list of untranslated don't
forget to save the changes using the save button (or keybinding).

There are also other useful possibilities to keep track of new translations.
Check them out here:
Keeping track of new translations

Previous
Checks/Issues
Next - Integration
Getting started

Last modified 9mo ago
Copy link
Contents
Getting the job done