Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Internationalization for react done right. Using the i18next i18n ecosystem.

License

NotificationsYou must be signed in to change notification settings

i18next/react-i18next

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CICode ClimateCoverage StatusQualitynpm

IMPORTANT:

Master Branch is the newest version using hooks (>= v10).

$>=v10.0.0npm i react-i18next

react-native: To use hooks within react-native, you must use react-native v0.59.0 or higher

For the legacy version please use thev9.x.x Branch

$ v9.0.10 (legacy)npm i react-i18next@legacy

Documentation

The documentation is published onreact.i18next.com and PR changes can be suppliedhere.

The general i18next documentation is published onwww.i18next.com and PR changes can be suppliedhere.

What will my code look like?

Before: Your react code would have looked something like:

...<div>Just simple content</div><div>  Hello<strongtitle="this is your name">{name}</strong>, you have {count} unread message(s).<Linkto="/msgs">Go to messages</Link>.</div>...

After: With the trans component just change it to:

...<div>{t('simpleContent')}</div><Transi18nKey="userMessagesUnread"count={count}>  Hello<strongtitle={t('nameTitle')}>{{name}}</strong>, you have {{count}} unread message.<Linkto="/msgs">Go to messages</Link>.</Trans>...

📖 What others say

Why i18next?

  • Simplicity: no need to change your webpack configuration or add additional babel transpilers, just use create-react-app and go.
  • Production ready we know there are more needs for production than just doing i18n on the clientside, so we offer wider support onserverside too (nodejs, php, ruby, .net, ...).Learn once - translate everywhere.
  • Beyond i18n comes withlocize bridging the gap between development and translations - covering the whole translation process.

ecosystem

Localization workflow

Want to learn more about how seamless your internationalization and translation process can be?

video

watch the video

Installation

Source can be loaded vianpm ordownloaded from this repo.

# npm package$ npm install react-i18next
  • If you don't use a module loader it will be added towindow.reactI18next

Do you like to read a more complete step by step tutorial?

Here you'll find a simple tutorial on how to best use react-i18next.Some basics of i18next and some cool possibilities on how to optimize your localization workflow.

Examples

v9 samples

Requirements

  • react >=16.8.0
  • react-dom >=16.8.0
  • react-native >=0.59.0
  • i18next >=10.0.0 (typescript users: >=17.0.9)

v9

Core Contributors

Thanks goes to these wonderful people (emoji key):


Jan Mühlemann

💻💡👀📖💬

Adriano Raiano

💻💡👀📖💬

Pedro Durek

💻💡👀💬

Tiger Abrodi

💻👀

This project follows theall-contributors specification. Contributions of any kind are welcome!


Gold Sponsors


localization as a service - locize.com

Needing a translation management? Want to edit your translations with an InContext Editor? Use the original provided to you by the maintainers of i18next!

locize

By usinglocize you directly support the future of i18next and react-i18next.



[8]ページ先頭

©2009-2025 Movatter.jp