i18next documentation
🏠 i18next🌐 localization as a service🎓 i18next crash course💾 GitHub Repository
  • 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
On this page
  • How all began - back in 2011
  • V2
  • Internationalization (i18n) is not enough
  • locize to the rescue
  1. Misc

The history of i18next

Last updated 1 year ago

How all began - back in 2011

All started back in 2011 when we were in search for an internationalization library that meets our demand - allowing to run both on server side and on our client side single page applications.

V2

With v2 of i18next, released in 2015, we completely rebuild i18next to be as extensible as possible.

Internationalization (i18n) is not enough

Our community provided us with great feedback. Out of that response and our own experiences we learnt providing instrumentation for doing proper internationalization just is not enough.

Helping developers to get their applications translated is great - but there is more to it.

  • How do you integrate any translation services / agencies?

  • How do you keep track of new or removed content?

  • How do you handle proper versioning?

  • How do you deploy translation changes without deploying your complete application?

  • and a lot more...

  • Manage the translation files with ease

  • Analytics & Statistics

  • and a lot more...

I18next was born and fastly grown to one of the most used frameworks for translating web applications and in . The response of the community was amazing and a fast growing established itself around i18next.

Since v1 all newer releases can be dropped in as a replacement for v1 by just adding a minimal compatibility layer. The v1 API is still actively tested, .

Shortly after the i18next v2 release in 2015, another big community driven i18next extension was released: .

to the rescue

Having created the foundation with i18next it was a long journey to .

Continuous deployment? with a !

🙏 The best way to directly support the future of i18next is to use . 💙

<<We aim to simplify localization, making it an efficient process that aligns with the ever-evolving demands of the modern business landscape.>> .

Node.js
ecosystem
here
react-i18next
locize
localization as a service
Easy to integrate
Continuous localization
CDN
Order professional translations
Profit from a content delivery network
Versioning of your translations
Automatic and On-Demand Machine Translation
Risk free: Take your data with you
Transparent and fair pricing
locize
read the full interview
Node.js
The first i18next landing page in 2011: http://i18next.github.io/i18next/
https://www.npmtrends.com/react-i18next-vs-i18next