Skip to content
This repository was archived by the owner on May 19, 2022. It is now read-only.
/ vue-i18next Public archive

Internationalization for vue using the i18next i18n ecosystem.

Notifications You must be signed in to change notification settings

panter/vue-i18next

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c620d8e · May 19, 2022
May 30, 2018
Jun 12, 2019
Jun 12, 2019
Jan 30, 2020
Jan 30, 2020
Jan 26, 2019
Jan 26, 2019
Apr 23, 2017
Jun 12, 2019
Jun 12, 2019
Apr 23, 2017
Sep 20, 2018
Sep 20, 2018
Sep 20, 2018
May 19, 2022
Jun 12, 2019
Jan 26, 2019
Jan 26, 2019
Jun 12, 2019

Repository files navigation

DEPRECATED, please use https://github.com/i18next/i18next-vue ! Thanks for your support!

vue-i18next

Build Status Coverage Status semantic-release

Internationalization for vue using the i18next i18n ecosystem. https://panter.github.io/vue-i18next/

Introduction

18next goes beyond just providing the standard i18n features such as (plurals, context, interpolation, format). It provides you with a complete solution to localize your product from web to mobile and desktop.

vue-i18next is the vue support for i18next and provides:

  • Component based localization
  • Component interpolation
  • Lazy load namespaces
  • Namespaced translation for components

Requirements

  • vue >= 2.0.0
  • i18next >= 6.0.1

Documentation

See here

Init

import Vue from 'vue';
import i18next from 'i18next';
import VueI18Next from '@panter/vue-i18next';

Vue.use(VueI18Next);

i18next.init({
  lng: 'de',
  resources: {
    ...
  }
});

const i18n = new VueI18Next(i18next);
new Vue({
  ...
  i18n: i18n,
});

Changelog

Detailed changes for each release are documented in the releases.

Issues

Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.

Contribution

Please make sure to read the Contributing Guide before making a pull request.

License

MIT