ps-js/i18n-editor

GUI for editing your i18n translation files

i18n-editor

This application lets you manage multiple translation files at once.
The editor supports translation files with the following format:

• JSON
• ES6 (JSON wrapped in a javascript ES6 module)
• Properties (java properties files, for example to be used for a ResourceBundle).

Features

• Editing multiple translation files at once.
• Creating new translations/locales or editing existing ones.
• Renaming, duplicating, creating or deleting individual translations.
• Detecting missing translations.
• Minifying translations on save.

Requirements

The application requires java 8 to be installed on your system.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

Download

You can download the latest release by going to this page and downloading the .zip file.
If you're on Windows you can install the application by running the .exe file. If you're on Mac you can use the application by running the .app file. If you're on Linux you can use the application by running the .jar file.

Usage

Getting started

To start, open the application and go to File > New Project to create a new project. After choosing the desired file format for your translations, select the root directory where you want to store your translation files. After selecting the root directory you'll be asked to add your first locale. From here you can add more locales by going to Edit > Add Locale... or start adding translations either via Edit > Add Translation..., via the right click menu in the left side panel or via the key field at the bottom of the left side panel. Each time you start the editor it will open the last project you was working on. You can always import an existing project by going to File > Import Project... and selecting the root directory of your existing project.

Translation files

By default translation files of the format JSON or ES6 will be saved in locale directories with the filename translations.json or translations.js respectively. Translation files of the format Properties will be saved with the locale embedded in the filename, for example translations_nl_NL.properties. The Properties formatted files also differ from the other formats in that it will create a default translation file called translations.properties, this is the fallback translation file (which is common for a java ResourceBundle).

Translation status

In the tree on the left side of the editor translations with missing values will be marked with a yellow icon in front of them.

Settings

You can access the settings of the editor by going to Settings > Preferences.... Here you can change the filename of the translation files you want to use (by default they are named translations), select whether you want to minify the files on save and change interface related properties. Some of this settings can also be applied on each project individually via Settings > Project Preferences....

Help translating

Do you want this editor to be in your native language? You are free to create a pull request or issue with a new translation file of your desired language. Take a look at src/main/resources/bundles on how to create a translation file.

License

This project is released under the MIT license.