babelfish
i18next
| babelfish | i18next | |
|---|---|---|
| - | 63 | |
| 254 | 7,721 | |
| -0.4% | 1.0% | |
| 0.0 | 9.0 | |
| over 1 year ago | 10 days ago | |
| JavaScript | 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.
babelfish
We haven't tracked posts mentioning babelfish yet.
Tracking mentions began in Dec 2020.
i18next
-
Advanced Frontend Resources for Next.js Development 🚀
🌍 i18next Documentation
-
How to Easily Add Translations to Your React Apps with i18next
i18next is a popular internationalization library for JavaScript applications. It provides a robust framework for managing translations, formatting dates, numbers, and handling pluralization. i18next supports multiple backends for storing translations, making it versatile and adaptable to various project requirements.
-
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/)
What are some alternatives?
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
polyglot - Give your JavaScript the ability to speak many languages.
Screen-Translator - An Electron.js-based desktop application for automatically translating on-screen text.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
i18n-node - Lightweight simple translation module for node.js / express.js with dynamic json storage. Uses common __('...') syntax in app and templates.
indent-string - Indent each line in a string
deepl-translator - This module provides promised methods for translating text using DeepL Translator (https://www.deepl.com/translator) undocumented API.