New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement: Option to change a string in all languages simultaneously #16
Comments
Thanks! You can already do this (almost as efficiently as you described):
|
Thanks, I'll try that. |
Unfortunately this does not help. When entering a new (or renewed) phrase all I can do is enter the text for the default language. I still have to open each language seperately to add translations. |
Well, it's difficult to add this to the user interace. How would you do it? Would it help if you could jump from the phrase in one language directly to the phrase in another language? This means that you wouldn't have to navigate to the right page and position for the second language ... |
Why not allow changing all translations of a single key at the screen where you can untranslate and delete it or change it's group assignment? Since you already have the key there, it should not be hard to add a table with all the translations there. |
There's not really enough space there for the phrase in 95 languages -- even more so if you are editing a I still think that a direct link to the phrase's row in another language may be the best tradeoff. |
Yes, that might be the best option. |
One task I do quite often is to change single strings in all languages to adapt to changes in my app.
Currently I have to open every language supported on it's own, search for the string, change it and save and approve it. This becomes quite time consuming and boring even with the 12 languages I support now, let alone for somebody featuring more languages.
Suggestion: Introduce the option to search for a key and edit the localized strings for it on one page, including approval. This should probably only be possible for the project owner, not members.
For a single developer like me who translates most languages on his own this would be a great functionality to cut down time spent on localization.
The text was updated successfully, but these errors were encountered: