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?

I18n Formats

We work on extending the list of supported i18n formats. If you need an i18n format and can't find it here send us an email.

Depending on the format it comes with different support functionality helping you with correct syntax.

All events listed here, will be notified.

The chosen i18n format will always be respected. There is no sort of i18n format conversion while importing from or exporting to one of the supported file formats.
You can learn more about the different i18n formats here.

i18next / locizify

https://www.i18next.com/

https://github.com/locize/locizify

  • Syntax Highlighting: Highlighting of format-specific syntax
  • Plural Conversion: Automatically generates plurals as needed
  • Grouping: Segments get grouped by plurals (and context if choosing the ext variant)

On this page you can find more information about the V4 JSON format and the V3 JSON format.

ICU / messageformat

http://userguide.icu-project.org/formatparse/messages

  • Syntax Highlighting: Highlighting of format-specific syntax

fluent

https://projectfluent.org/

  • Syntax Highlighting: Highlighting of format-specific syntax

vue-i18n

https://kazupon.github.io/vue-i18n/

  • Syntax Highlighting: Highlighting of format-specific syntax

i18n.js / ruby

https://github.com/fnando/i18n-js

  • Syntax Highlighting: Highlighting of format-specific syntax
  • Plural Conversion: Automatically generates plurals as needed
  • Grouping: Segments get grouped by plurals

polyglot

https://airbnb.io/polyglot.js/

  • Syntax Highlighting: Highlighting of format-specific syntax

android

https://developer.android.com/guide/topics/resources/localization

  • Syntax Highlighting: Highlighting of format-specific syntax
  • Plural Conversion: Automatically generates plurals as needed
  • Grouping: Segments get grouped by plurals