vue-i18n
i18next
Our great sponsors
vue-i18n | i18next | |
---|---|---|
7 | 60 | |
7,223 | 7,399 | |
- | 1.7% | |
6.5 | 9.2 | |
3 months ago | 15 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.
vue-i18n
- Syntaxe francophone
-
Alternative libs to migrate from React to Vue (or Vue to React)
vue-i18n
-
A better way to manage translations for software projects
Your working in a team on a software project. The user interface needs to support multiple different languages, so your team either picks an open source tool for this (next-translate, typesafe-i18n, vue-i18n, etc), or depending on your development framework, internationalization features might be baked right in (IOS, Android, AngularJs, etc).
-
What is the best practice for multi-lingual small single-page applications/websites?
You want internationalization or i18n support. I use this: https://kazupon.github.io/vue-i18n/ which is the official plugin.
-
Top 10 Vue.js Resources For Your Project 🚀
Kazupon is a well-known developer at Vue.js. He is also the creator of Intlify, known for its contribution to the software internationalization space, which has created an internationalization plugin for Vue.js known as Vue I18n.
-
Vue 3 localization
I use vue-i18n and it works well for my web app. It took a little bit of fiddling to get it to work with the Composition API, to build a language switcher component, and to set up lazy loading of language files. I followed their examples for Locale changing and Lazy loading translations, and I'm happy with the result.
-
How to make internationalization your website on Vue@3 and Vue-i18n@9
This source code was implemented based on Vue I18n official Guide and Issues on its Github repository.
i18next
-
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.
-
Fastest way to unleash the full power of i18next
Internationalization (i18n) and localization (l10n) are crucial for businesses that want to expand globally and reach a wider audience. To do this, you need a robust solution that can handle different languages and cultural nuances, and this is where i18next and locize come in. These two elements have been designed to help you get the most out of your i18n efforts, and when used together, they are a powerhouse combination that can help you achieve your goals faster and more efficiently. In this video, we'll explore the fastest way to unleash the full power of i18next.
What are some alternatives?
vue-meta - Manage HTML metadata in Vue.js components with SSR support
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
vee-validate - ✅ Painless Vue forms
polyglot - Give your JavaScript the ability to speak many languages.
fluent-vue - Internationalization plugin for Vue.js
Screen-Translator - An Electron.js-based desktop application for automatically translating on-screen text.
javascript-i18next-example - Example repository demonstrating how to integrate Localazy with your javascript app using the i18next library
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
i18n - I18n module for Nuxt
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
vue-wait - Complex Loader and Progress Management for Vue/Vuex and Nuxt Applications
deepl-translator - This module provides promised methods for translating text using DeepL Translator (https://www.deepl.com/translator) undocumented API.