do not store `.ui` lines in `.ts` files
Without the lines the files will only change if the actual strings change and can properly be committed instead of doing the non-sensical task of just updating them right before a release.
We could also specify -locations none and it would also get rid of the file is originates from reducing the chance of it being modified even more.
@fu7mu4 I have never worked with translations and it seems you are the last remaining contributor in that area. Will the lack of that information cause any issues working with translations?
I basically approve this.. however well I assume that theoretically it could cause problems if a ui file would contain the same string in english in two places and the translator wants to translate to different strings.
I basically approve this.. however well I assume that theoretically it could cause problems if a ui file would contain the same string in english in two places and the translator wants to translate to different strings.
That seems unlikely (although from a linguistic view it definitely isn't).
I have not checked the changes if it eliminated some strings. I also thought of some potential problematic cases which I can no longer recall. I hope the contributor feedback will give more insights.
We could also specify -locations none and it would also get rid of the file is originates from reducing the chance of it being modified even more.
I have never understood how that really works anyway. If the same string appears 3 times in a source file and is translated into 3 different strings.. then developer refactors the code.. the same strings still appear but in changed locations.. I don't understand how qt can be sure that the correct translations will be matched.
A basic refactoring is that some functions are moved so that the strings do not appear in the same order anymore.
Idea to prevent problems: I believe it would be simple to write a small script that checks the ts files.. if the same string should be translated into different translated strings then write error message.. we will then have to look into that and see what we can do about it. If the script is happy then removing ui and locations should be safe?