|
2 | 2 |
|
3 | 3 |    |
4 | 4 |
|
5 | | -A minimal, but complete solution for managing translations, date and number formatting in Next.js apps. |
| 5 | +A minimal, but complete solution for managing translations, date, time and number formatting in Next.js apps. |
6 | 6 |
|
7 | 7 | This library complements the [internationalized routing](https://nextjs.org/docs/advanced-features/i18n-routing) capabilities of Next.js by managing translations and providing them to components. |
8 | 8 |
|
9 | 9 | ## Features |
10 | 10 |
|
11 | | -- π I18n is an essential part of the user experience, therefore this library doesn't compromise on flexibility and never leaves you behind when you need to fine tune a translation. Messages use the proven [ICU syntax](https://formatjs.io/docs/core-concepts/icu-syntax) which covers interpolation, numbers, dates, times, plurals, ordinal pluralization, label selection based on enums and rich text. |
12 | | -- βοΈ Based on battle-tested building blocks from [Format.JS](https://formatjs.io/) (used by `react-intl`), this library is a thin wrapper around high-quality, lower-level APIs for i18n. |
13 | | -- π― Built-in number and date formatting that is integrated with translations, e.g. allowing for the usage of global formats for a consistent look & feel of your app. |
14 | | -- π‘ A hooks-only API ensures that you can use the same API for `children` as well as for attributes which expect strings. |
15 | | -- π Integrates with both static as well as server side rendering. |
| 11 | +- π I18n is an essential part of the user experience, therefore this library doesn't compromise on flexibility and never leaves you behind when you need to fine tune a translation. Messages use the **proven [ICU syntax](https://formatjs.io/docs/core-concepts/icu-syntax)** which covers interpolation, numbers, dates, times, plurals, ordinal pluralization, label selection based on enums and rich text. |
| 12 | +- π
Built-in **date, time and number formatting** provides all the necessary parts you need for localisation. You can use global formats for a consistent look & feel of your app and integrate them with translations. |
| 13 | +- π‘ A **hooks-only API** ensures that you can use the same API for `children` as well as for attributes which expect strings. |
| 14 | +- βοΈ Based on **battle-tested** building blocks from [Format.JS](https://formatjs.io/) (used by `react-intl`), this library is a thin wrapper around high-quality, lower-level APIs for i18n. |
| 15 | +- π By integrating with both **static as well as server side rendering** you always get the best possible performance from your app. |
16 | 16 |
|
17 | 17 | ## What does it look like? |
18 | 18 |
|
|
0 commit comments