some suggestions - Githubissues

jcbvm / i18n-editor

GUI for editing your i18n translation files

MIT License

357 stars 78 forks source link

some suggestions #15

Open basz opened 7 years ago

basz commented 7 years ago

some random thoughts here. no pressure. thanks for the hard work!

usability

~~selecting a row in the list of translation can only be done by click exactly on the word. More useful would be if one could click on the complete row.~~
~~a way to quickly go from translation to translation, even when the editor fields have focus via the keyboard.~~
CR to find and focus the next unfinished translation
tab to switch between translation fields + option/command + tab to switch between tranlation list or fields
~~translation field are a little big, perhaps size should be configurable. as most translations are oneliners~~

feature

translate via external services (https://ctrlq.org/code/19909-google-translate-api)

jcbvm commented 7 years ago

Thanks for you suggestions, will see what I can do 👍

shorstki commented 5 years ago

@jcbvm I would like to suggest option to save translation key/folders separately, so translation file can be divided into modules (useful for SPAs) and then into separate translation/locale files, like

{
  "HEADER": {
    "BACK": "Back
  }
}

Can be saved in i18n>header>en.json and the i18n is the main project folder. For other locale i18n>header>de.json