TU status information

Studio save TUs along with their ConfirmationLevel (translated, ApprovedTranslation etc.). Why is this information not displayed during translation? And it would be nice if you could use this info for filtering (penalties, export/import) etc.

Parents Reply Children
  • Hi Bruno,

    I see what you mean now... or rather I had never noticed this before at all!

    <prop type="x-ConfirmationLevel">Draft</prop>

    <prop type="x-ConfirmationLevel">Translated</prop>

    <prop type="x-ConfirmationLevel">RejectedTranslation</prop>

    <prop type="x-ConfirmationLevel">RejectedSignOff</prop>

    <prop type="x-ConfirmationLevel">ApprovedSignOff</prop>

    I did a little testing and as far as I can see it can hold these statuses above.  So now I have a couple of questions:

    • Why do we hold this at all as it's only visible in a Studio TMX export (not 2007 TMX)? One for  I think.
    • Why would you even add TUs with these statuses to your TM... apart from the "ApprovedSignOff" and "Translated"?
    • Wouldn't this all become very complicated if you wanted to set penalties with these after adding TUs that probably shouldn't be in your TM in the first place?  Surely it makes more sense to use these statuses in the bilingual file.  I cannot think of any good reasons for storing rejected, or draft TUs in the TM.

    I guess you have a good reason Bruno so I'm looking forward to being educated!!

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Paul,
    this might be useful in a scenario where you have translators and reviewers working simultaneously on the same project and you want users to be able to see which segments have been reviewed already. And yes, the interesting status would be "translated", "translation approved" or "signed off". Achieving this with penalties is much more complicated (with many users and various options "last used by/last modified by" etc.).
    Bruno