π Better Vue i18n experiences with VSCode
- Inline annotation
- i18n key autocomplete
- Friendly UI for managing locales
- One-click machine translation
- Extract text from code
- JSON and YAML supported
- Multi-root workspace
- Translating progress
- Supporting both
vue-i18n
,vuex-i18n
andvue-i18next
- Install
vue-i18n
package if you haven't yet.npm i vue-i18n
oryarn add vue-i18n
- Install this extension
locales
path will be detected automatically. You can also configure it manually. There are two ways to do that:- Open Command Palette (
Ctrl-Shift-P
orββ§P
), typeVue i18n Ally: Manual configure locales path
then press enter and follow the guide. - Modify the
settings.json
file of your VSCode, addingvue-i18n-ally.localesPath
manually.
- Open Command Palette (
You can have locales directory structured like this
locales # you can specify the folder path in the settings
βββ en.json
βββ de-DE.json
βββ zh-CN.yaml # YAML is also supported
βββ zh-TW.yaml
βββ ...
βββ <contry-code>.json
or
locales
βββ en
| βββ common.json
| βββ buttons.json
| βββ ...
| βββ <filenames>.json
βββ de-DE
| βββ common.json
| βββ buttons.json
| βββ ...
βββ <contry-code>
βββ common.json
βββ buttons.json
βββ ...
Currently we support json
or yaml
as your locales file type.
If you would like use different file formats or directory structures, it welcome to open an issue or pull request.
- Machine translating
- Locales Tree
- Translating progress
- Workspace support
- Underscore for i18n keys?
- YAML support
-
$tc
,$d
,$n
,v-t
support - Hide/Show specific locales
- Screenshots
- Language flags
- Vue inlined locales support
- Source language indicator
- Analysis report
- JSON/YAML file annonation & hint
- Annoation config (on/off, maxlength)
- Force enabled on non-vue-i18n project
- i18n for the plugin itself
-
.js
locales - tests
This extension is original forked from think2011/vscode-vue-i18n, it can't be existed without @think2011's great work.
MIT License Β© 2019 Anthony Fu
MIT License Β© 2018-2019 think2011