So far a small change in a large text block forces the translators to re-translate the whole block. In the enroute_xx.ts files the old text is just marked 'vanished', and there is no hint which part of the text has been changed (nor does Qt Linguist provide any hint). The changes are often very small, e.g. adding a new team member below the old text.
The aim is to split large text areas into smaller portions. Advantage: More transparency and way less time needed for the translators. Additional goody: less frustration due to translating the same text for the 7th time.
Of course copy & paste would help BUT for using copy & paste it would be indispensable to know where exactly the change has been made.
Suggestion for the AUTHORS part: see file aut1.txt ... aut4.txt (not immediately, but when the next change or addition is to be made):
kebekus
commented
1 year ago
So far a small change in a large text block forces the translators to re-translate the whole block. In the enroute_xx.ts files the old text is just marked 'vanished', and there is no hint which part of the text has been changed (nor does Qt Linguist provide any hint). The changes are often very small, e.g. adding a new team member below the old text.
The aim is to split large text areas into smaller portions. Advantage: More transparency and way less time needed for the translators. Additional goody: less frustration due to translating the same text for the 7th time.
Of course copy & paste would help BUT for using copy & paste it would be indispensable to know where exactly the change has been made.
Suggestion for the AUTHORS part: see file aut1.txt ... aut4.txt (not immediately, but when the next change or addition is to be made):
Upcoming text sections should be kept reasonably short, of course considering text coherency. aut1.txt aut4.txt aut3.txt aut2.txt