• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 2640 views
  • Users 0 members are here
Options
Related

TU status information

Bruno Ciola

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.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Bruno,

    Studio does not save TUs along with their confirmation level. What made you think this? The confirmation levels are held in the bilingual file (sdlxliff). If Studio did hold this then you would potentially have 4 or 5 duplicate TUs separated only by their status... so you could filter on it!

    If you want to do this you could create an attribute to the TM based on the status and update the TUs each time with the appropriate status. But I really don't see the value in this at all. Can you elaborate?

    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

  • 0 in reply to Paul
    Hi Paul,
    when you export a tmx file from a Studio TM each segment has a ConfirmationLevel info, so I suppose this information is stored in the TM as well (otherwise where would it come from)? Using this information rather than field values seems to me much easier (no project settings to change etc.).
    Regards
    Bruno
  • 0 in reply to Bruno Ciola

    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

  • 0 in reply to Paul
    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
Reply Children
No Data