When do I usually use an update for a new version?
Angesagt
I wonder when I use “update new version”. Does it usually happen after a project finished and a new version of the project comes, or when a project is being translated and a new version of project comes, in which scenario is it usually used?
If it’s the first case, can we get perfect match from old version’s translations? And the new version’s data (like wordcount etc.) will overwrite the old ones, right?
If it’s the second case, will the translation done in the old project will be leveraged to the new version’s files very easily?
-
Versioning can be used in both cases :
1) After the translation is over
2) As the freelancer is in the middle of his work.
In both cases, the translator will get notified, as the job’s status will have changed.
All past translations will be marked as elements coming from the preceding version and further information about the context is granted to the him. The progress bar will get updated as well with another color for all those former translations. Wordcount will be updated as well with all information about past and new version.
1) Freelancer accepts the job and translates the original version of the document. (screenshot 1)
2) The source file is updated but the job is no longer an open task (crowd), unless you want new versions to always follow the Project default workflow. (see screenshot 2)
3) By “re-accepting” the job, the translators specifies that he noticed that a new version has been brought in. (see screenshot 3)
4) The translator can keep on working and knows that he is working on the 2nd version of the document. (see screenshot 4)
5) All ongoing/past translations are kept. Further information about the context is granted to the translator and the progress bar will get updated as well with another color for all elements “pre-translated from a preceding version”. (see screenshot 5 & 6)
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar