Skip to content
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.

some suggestions #15

Open
basz opened this issue Feb 6, 2017 · 2 comments
Open

some suggestions #15

basz opened this issue Feb 6, 2017 · 2 comments

Comments

@basz
Copy link

basz commented Feb 6, 2017

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

@jcbvm
Copy link
Owner

jcbvm commented Feb 7, 2017

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

@shorstki
Copy link

shorstki commented May 21, 2019

@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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants