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 vs. i18next

i18n stands for "internationalization," which is the process of designing and developing a software application or website in a way that allows it to be easily adapted for different languages and regions without requiring significant changes to the underlying code. This involves separating the user interface strings, date formats, currency symbols, and other locale-specific elements from the main codebase. Instead of hardcoding these elements, developers use placeholders that can be replaced with the appropriate values based on the user's language and location.

i18next, on the other hand, is a specific JavaScript library that helps developers implement internationalization in their applications. It provides tools and features to manage translations, handle pluralization, manage language fallbacks, and more. i18next makes it easier for developers to implement internationalization best practices without having to build these features from scratch.

In essence, i18n is a broader concept that refers to the practice of adapting software for different languages and regions, while i18next is a specific tool or library that facilitates the implementation of internationalization within JavaScript-based applications. It's like i18next is a tool that helps you achieve i18n in your projects.

When using i18next, you generally integrate it into your codebase and configure it to handle various aspects of internationalization. It provides an API that allows you to load and switch between different translations, manage placeholders, and handle other localization-related tasks.

In summary, i18n is the concept of making software adaptable to different languages and regions, while i18next is a specific library that aids in implementing this concept within JavaScript applications.

On this page