You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Clean and readable - Keep your code clean and readable, while the library uses battle-tested and powerful ICU MessageFormat under the hood. Universal - Use it everywhere. @lingui/core provides the essential intl functionality which works in any JavaScript project, while @lingui/react offers components to leverage React rendering, including React Server Components (RSC) support, and @lingui/solid b
Read here about how to add the namespaces JSON files. Next-translate ensures that each page only has its namespaces with the current language. So if we have 100 locales, only 1 will be loaded. In order to do this we use a webpack loader that loads the necessary translation files inside the Next.js methods (getStaticProps, getServerSideProps or getInitialProps). If you have one of these methods alr
Asymmetric Localization Natural-sounding translations with genders and grammatical cases only when necessary. Expressiveness is not limited by the grammar of the source language. Progressive Enhancement Translations are isolated; locale-specific logic doesn't leak to other locales. Authors can iteratively improve translations without impact on other languages. Fully-Featured Date, time, and number
The JavaScript Intl library (ECMA 402) has used strings to identify locales since the beginning. This works well for many simple cases, and is lightweight and user-friendly. ICU uses a Locale class instead. Defining a Locale class allows the following: Parsing and manipulating the language, region and script of a locale Reading or writing the Unicode extension tags in a locale A serializable, stan
![GitHub - tc39/proposal-intl-locale: `Intl.Locale` specification [draft]](https://cdn-ak-scissors.b.st-hatena.com/image/square/6f05f54b92fca5bc5c0a6927fd7b45f1ee01a8c2/backend=imagemagick;height=288;version=1;width=512/https%3A%2F%2Fproxy.goincop1.workers.dev%3A443%2Fhttps%2Fopengraph.githubassets.com%2F3b2f463f87bb05b1c6355ad508154e413a4a61f8a4d50e1751564cd208009dfb%2Ftc39%2Fproposal-intl-locale)
サービスを海外展開したい場合、国際化対応を行う必要性がある。これをi18n対応と呼ぶ。Reactでフロントエンドを構築する場合、i18nのための多くのライブラリがあるが、yahoo製の react-intl が実質デファクトスタンダードだ。react-intlを実際に使っている例として、スター14000超えのReactボイラープレートであるreact-boilerplate やSNSの マストドン がある。 しかし、実際にreact-intlを使うとidの管理が非常に面倒であることがわかる(他すべてのi18nライブラリも同様だが)。react-boilerplateを参考にidの管理を見てみる。 まず、react-boilerplateでは、ディレクトリベースでコンポーネントを管理している。その中で、messages.jsにdefineMessagesを使いidとデフォルトメッセージを定義
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
quilt/packages/address at main · Shopify/quilt
