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?

Is it possible to integrate multiple projects in the same app/website?

Yes, this is possible, you can combine any project you want on your side.Just have a look at our API, and use the appropriate endpoint with the appropriate project-id.

Using i18next?

With i18next you can configure fallback backends to be used . This way you can simply add the i18next-locize-backend multiple times and pass in the appropriate options. This is all possible thanks to the chained backend.

import i18next from "i18next";
import ChainedBackend from "i18next-chained-backend";
import LocizeBackend from "i18next-locize-backend";

i18next
  .use(ChainedBackend)
  .init({
    fallbackLng: "en",
    // ... your i18next config
    backend: {
      backends: [
        LocizeBackend,
        LocizeBackend
      ],
      backendOptions: [
        { // first project
          projectId: "[PROJECTID]",
          version: "[VERSION]",
          referenceLng: "en"
        },
        { // second project
          projectId: "[PROJECTID]",
          version: "[VERSION]",
          referenceLng: "en"
        }
      ]
    }
  });

Make sure your projects contain different namespace names.
i.e.
   project 1: common, header, blog
   project 2: extended, mails, templates

The i18next-chained-backend will always take the first backend that returned some data. It will not check if the key you're looking for is present in the namespace.

We suggest not to use multiple backends in combination with saveMissing or updateMissing, because it may happen, that the trigger for this is based on stale data.

App / Website splitted in app specific and framework translations.

If you have some sort of shared component, like an own framework or a core module, which is shared accross multiple applications, we suggest to use separate i18next instances, each instance references its own locize project.

On this page