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?

Why is my namespace suddenly a flat json?

locize serves flat or nested json depending on the keys in the resource.

Suppose, you have most keys in your translation following the nested scheme (e.g. "login.label", "login.user", etc), then locize serves a resource with nicely nested json:

{
    "login": {
        "label": "Log in",
        "user": "User Name"
    }
}

If you now add a key that does contain a space, comma or question mark / |,|\?/. ("User not found!"), then the resource returned by locize becomes flat:

{
    "login.label": "Log in",
    "login.user": "User Name",
    "User not found!": "User not found!"
}

locize automatically transforms to this flat format if it detects that keys use natural language. This is the default behaviour.

If you know that you always use flat format, you can select this in the developer settings of your project.

How to change the publish format?

On this page