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?

Translation Memory

A translation memory (TM) is a database that stores sentences, that have previously been translated, in order to aid human translators.

Smart translation memory

In contrast to traditional translation memories the implementation inside locize brings following benefits:

  • better performance - the translation memory runs directly in your browser and provides faster results by not having to roundtrip to the server
  • the translation memory can be configured to use multiple projects - so you can reuse translations from all your existing projects
  • the translation management search works not only on exact language pairs but also shows results for languages of the same family, eg. en-GB results while you search in en-US
  • every result has a link back to it's source project which makes maintaining the memory and keeping translation consistency a breeze

Configuration of the translation memory

You can configure your translation memory by navigating to your project settings page, in the "EDITOR, TM/MT, ORDERING" tab and clicking the "Translation Memories" section in the "Cat settings" card. On new projects the service is enabled by default and the project itself is selected as translation memory source.

In the settings you can add / remove projects which should be used as translation memory source.

The translation memory will be loaded on startup and will be cached for 24h in your browsers indexedDB.

Using the translation memory

On every segment on the right side you will see the results in the appropriate tab. Clicking it will enable a translation memory lookup for this segment.

On every match you can accept the translation memory entry by just clicking it.

Check this section in the video to see how the Translation Memory can be used.

translation memory part of showcase/demo

Are you working with multiple versions? Be aware that only the content of the published latest version of the referenced translation memory project is used.