i18next documentation
🏠 i18next
🌐 localization as a service
🎓 i18next crash course
💾 GitHub Repository
Search
⌃
K
Links
Introduction
Overview
Getting started
Comparison to others
API
Configuration Options
Supported Frameworks
Plugins and Utils
For Enterprises
First setup help
TypeScript
Translation Function
Essentials
Interpolation
Formatting
Plurals
Nesting
Context
Objects and Arrays
Principles
Best Practices
Translation Resolution
Namespaces
Fallback
Plugins
How to
Add or Load Translations
Extracting translations
Caching
Backend Fallback
FAQ
Misc
JSON Format
Creating own Plugins
Migration Guide
The history of i18next
Testimonials
🌐
localization as a service
🎓
i18next crash course
💾
GitHub Repository
Powered By
GitBook
Testimonials
<<How we translated the Avocode website written in Next.js with the i18next package
...>>
<<...
Using i18next as our international framework enables us to use the same technology around our whole software stack, regardless the actual backend or framework we use. locize is the icing on the cake – it made translation management unspeakably easier.
...>
<<...
We have separated help pages for en, ja, zh, zh-TW. i18next automatically switched the link to appropriated lang help’s page
....>>
<<Using locize and its tools (i18next) saves us a LOT of time by not thinking about the texts and focusing on development only.
...>>
<<...
We used i18next with React and were translating JSON files by hand, which was really cumbersome.
...>>
<<...
Switching to locize was pretty straightforward, thanks to i18next and the possiblity to import JSON files in the admin dashboard.
...>>
<<...
Support was also very reactive and fixed a bug in under 1 hour after it was reported. I would recommend for use with i18next on a React.js platform.>>
<<...
We use i18next as an internationalization framework. locize being perfectly integrated with the framework become a really good translation management tool for us.
...>>
<<...
Using i18next in conjunction with react-i18next (there’s an Angular, Vue and even jQuery support, among others) will help you maintain expressive code that’s i18n ready.
...>>
Misc - Previous
The history of i18next
Last modified
7mo ago