Skip to content
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

Allow purging messages to keep existing translations #525

Closed
multiwebinc opened this issue Nov 6, 2019 · 1 comment · Fixed by #565
Closed

Allow purging messages to keep existing translations #525

multiwebinc opened this issue Nov 6, 2019 · 1 comment · Fixed by #565

Comments

@multiwebinc
Copy link
Contributor

When you do a scan for messages and check the "purge all messages first", this deletes everything, including existing translations, before re-adding the strings the scanner finds. And if you don't check the "purge all messages" box, any time you update a translation in the source files will create an extra message to be translated.

You are therefore left with two choices; check the box and have to re-translate everything again, or not check that box and end up with a bunch of ghost strings that are not found anywhere in the project. Neither of these cases is ideal and both will necessarily cause extra work for translators.

Here are my two suggestions:

  • Add an option to purge only the strings that are not still in the project.
  • Add a column to the list view to indicate that the string couldn't be found in the project anymore to give the translator an idea which strings can be safely deleted.
@mjauvin
Copy link
Contributor

mjauvin commented Nov 12, 2019

@multiwebinc any chance you could submit a PR for the proposed suggestion(s) ?

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

Successfully merging a pull request may close this issue.

2 participants