core
i18next
core | i18next | |
---|---|---|
27 | 61 | |
4,467 | 7,399 | |
0.5% | 0.8% | |
1.5 | 9.2 | |
2 months ago | 17 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
core
- Support for 40 locales on angular 17 standalone - how?
-
Coping with i18n
Some libraries support ways to handle missing translations (e.g., TranslocoMissingHandler from Transloco or MissingTranslationHandler from ngx-translate). So that's a way to find out any missing translations, but that's quite manual because you have to go over every part of the served application.
-
Differences ngx-translate vs i18n
ngx-translate
-
Angular 16 Unveiled: Discover the Top 7 Features
It was rather painless. We are using ngx-translate which seems dead at this point but works fine in 16 (seems to have gotten a recent commit).
- Angular 6 - i18n vs. ngx-translate
-
migrating old project to angular, need advice and recommendation on best practices
The problem with Angular 15 was the Ivy engine. And it wasn't fixed, maybe you're not affected. https://github.com/ngx-translate/core/issues/1185
-
Is the official angular/@localize i18n lib really the go to for localization?
He talks about it more here: https://github.com/ngx-translate/core/issues/783
-
i18n in angular
Ngx-translate is not updated anymore. Latest version is a year old. It's still not abandoned but it seems like the developer moved on to work on Angular i18n.
-
What's needed for ionic internationalization?
Just to refer to the original docs: https://github.com/ngx-translate/core
-
Dynamic translations in Angular made possible
One of the common pitfalls when using i18n are large translation files size and inability to split them in order to hide parts of your application from prying eyes. Some solutions like Angular built-in implementation are really powerful and SEO compatible but require a lot of preparation and do not support switching languages on the fly in development mode (which was causing troubles at least in version 9); other solutions like ngx-translate require you to install several packages and still donβt support splitting up a single language.
i18next
-
Implementing Internationalization (i18n) in Vue.js Projects
For this article, we'll leverage the 'Simple CRM' project from our previous list of projects. We'll integrate and utilize the i18n library to internationalize our application.
-
Translating zod errors with next-intl
When starting a new project with Next.js these days, next-intl and zod are my go to libraries for internationalization and schema validation, respectively. Of course, when using zod for client-facing validations I would like to translate potential error messages. The package zod-i18n can be used to achieve this for i18next, a popular alternative internationalization library. This means that by using this library as starting point one can quickly achieve zod translation with next-intl.
-
Top 20 Frontend Interview Questions With Answers
The best way to implement internationalization is to use an internationalization framework library, such as i18next. With this kind of library, you can easily handle translations and automatically display your frontend labels in the user's language. The frontend application also needs to be flexible and easily configurable so that its layout can change accordingly, reading from left to right or right to left. CSS allows this with the rtl and ltr CSS direction property.
-
Reactive translation/i18n
For reference, I am using i18next for providing translations, which is configured to use the english message string as a key for the translations and fallback to it if no translation is found in the chosen language. I also use the official svelte-i18next integration. It wraps the i18next object in a Svelte store and, among other things, provides reactivity when the language is changed.
-
Building a multilingual NextJS app using the new app directory
// app/components/BuiltInFormatsDemo.tsx 'use client'; import React from 'react'; import {useTranslation} from '../i18n/client'; import type {LocaleTypes} from '../i18n/settings'; import {useParams} from 'next/navigation'; const BuiltInFormatsDemo = () => { let locale = useParams()?.locale as LocaleTypes; const {t} = useTranslation(locale, 'built-in-demo'); return (
{/* "number": "Number: {{val, number}}", */} {t('number', { val: 123456789.0123, })} p>
{/* "currency": "Currency: {{val, currency}}", */} {t('currency', { val: 123456789.0123, style: 'currency', currency: 'USD', })} p>
{/* "dateTime": "Date/Time: {{val, datetime}}", */} {t('dateTime', { val: new Date(1234567890123), formatParams: { val: { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric', }, }, })} p>
{/* "relativeTime": "Relative Time: {{val, relativetime}}", */} {t('relativeTime', { val: 12, style: 'long', })} p>
{/* "list": "List: {{val, list}}", */} {t('list', { // https://www.i18next.com/translation-function/objects-and-arrays#objects // Check the link for more details on `returnObjects` val: t('weekdays', {returnObjects: true}), })} p> div> ); }; export default BuiltInFormatsDemo;
-
Supercharge Your TypeScript App: Mastering i18next for Type-Safe Translations
As our world becomes increasingly interconnected, the development of web applications that cater to a global audience takes precedence among developers. If you're a TypeScript developer, you're likely acquainted with the advantages of static typing and the assurance it provides in your codebase. When it comes to internationalization (i18n) and localization (l10n), maintaining the same level of type safety becomes crucial. This is precisely where i18next, an influential i18n framework, enters the picture.
-
localization in nextjs13
check i18next
-
Creating Multilingual React Apps with i18n: A Step-by-Step Guide to Internationalisation
In this article, we will go over how to perform internationalisation in our react app using the i18next framework. I18next is an internationalisation framework written in JavaScript. It comes with everything you need to localise your web, desktop or mobile product such as user language detection, loading and caching translations, and file conversion etc More features can be found in their documentation. (https://www.i18next.com/)
-
Change language in a website
Luckily this is a well-solved problem: https://www.i18next.com/
-
What is the best way to handle a multi-language site?
I am so sorry for all the people using https://www.i18next.com/ and manually defining string ids. Fuck that. I will never write another message id in my life.
What are some alternatives?
i18n-ally - π All in one i18n extension for VS Code
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
ng-zorro-antd - Angular UI Component Library based on Ant Design
polyglot - Give your JavaScript the ability to speak many languages.
transloco - π π The internationalization (i18n) library for Angular
Screen-Translator - An Electron.js-based desktop application for automatically translating on-screen text.
ngx-translate-messageformat-compiler - Advanced pluralization (and more) for ngx-translate, using standard ICU syntax which is compiled with the help of messageformat.js.
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
Mycodo - An environmental monitoring and regulation system
jsLingui - π π A readable, automated, and optimized (3 kb) internationalization for JavaScript
ng-conditional-validator - Angular library help you to build reactive forms dynamic validation
deepl-translator - This module provides promised methods for translating text using DeepL Translator (https://www.deepl.com/translator) undocumented API.