Search result not found.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

On this page

Locize Docs

Introduction

Using locize

Integration

Guides / Tips & Tricks

More

Which integration option should I use?Do I have to use the locize CDN or can I host / bundle the translations directly?How is locize different from the alternatives?Why do I get “The passed json is nested too deeply.” when consuming the API?Is locize only for developers and translators or is project management within the process too?What is the regular way to update the translation memory?Is there any visibility on project’s level of completion that shows how translators are progressing?Why is my namespace suddenly a flat json?How to change the publish format?Why does my namespace contain an array with a lot of null items?Why is the pricing so complicated?How to change credit card or billing information or download the invoices?How to import translations from a file?How to manually publish a specific version?How to delete or rename a namespace?Why is there such a high download amount?Where do I find the namespace backups?How can a segment/key be copied/moved or renamed?Why a new namespace is created, when I upload a translation file?I want to use the locize CDN, but would like to have a fallback that uses local/bundled translationsIs it possible to integrate multiple projects in the same app/website?Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?How do I open and edit JSON files?i18n vs. i18nexti18next vs. locizeWord CounterHow to style text within locize?What do I have to consider if my translation texts may contain confidential information?How to translate a file and download the results?

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 like translating 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

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:

On this page