Is there any way to ignore locked segments when Antidote verifier is used to check spelling/grammar?

Hello Community!

The agency I work with asks me not to touch previously translated segments with CM status.

However, I have a challenge when using Antidote during my QA phase. I've tried changing the status of CM segments from "translated" to "locked", but Antidote doesn't make any distinction as if a segment is locked or not, and still detects and suggests changes (for example, replacing a straight apostrophe with a typographical one, or changing a space to a non-breaking space).

In a large document, it's virtually impossible for me to determine which Antidote changes I have to avoid doing.

Am I the only one facing this kind of challenge? Any suggestions?

emoji
  • HI ,

    I'm currently working on renewing my Antidote license and test this occurrence. Please can you post a screenshot to show clarification over what is before and how it detects to change it using Antidote Verifier?

    Is it possible to have a small sample file for testing? 

    Also, what Studio and app version are you using?

    Regards,

    Oana

    Oana Nagy | 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

    emoji
  • Hi Oana,

    I finally was able to figure it out:

    Open the sdlxliff file in Studio.

    Before running Antidote, lock all the segments you want to protect from Antidote's changes (S3 and 4). In this document, I've also inserted a voluntary bug in S5, but haven't locked the segment so that Antidote's fix will be processed.

    Screenshot of RWS Trados Studio with a document open. The 'Antidote Verifier' button is highlighted in the toolbar. Arrows point to segments labeled 'NMT' indicating machine translation. No visible errors or warnings.

    Run Antidote from the Revision tab.

    The text in the locked segments will appear on Antidote screen as all text in all other segment types, and Antidote will detect errors for the whole document. You can fix all the errors without worry, because Studio will further prevent the locked segments from being updated, but will allow all other segment types to be updated.

    Screenshot of Antidote software showing a document with highlighted text. Errors are underlined in red, and alerts are underlined in blue. The right panel lists language errors and alerts with suggested corrections.

    When the verification is complete, go back to Studio.

    You will notice that Antidote has made corrections in some segments as their status will now be "draft" instead of "translated".

    Screenshot of RWS Trados Studio with a document open. Red arrows point to segments labeled 'NMT' indicating machine translation. A segment with a pencil icon indicates an edit. No visible errors or warnings.

    If the correction is correct, just confirm these segments (change their status from "draft" to "translated") and save the file.

    As for the locked segments, the original content remained intact because the "locked" status prevented the changes from being made.

    Screenshot of RWS Trados Studio with a document open. The 'Machine Translation' pane is visible with the title 'Accurate translations: Traductions precises'. No visible errors or warnings.

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 9:10 PM (GMT 1) on 28 May 2024]
  •  

    At the start of this year we made an improvement whereby if you filter for what you dont need (in your case locked segments) then run Antidote it respect your filtered segments only and disregard whats not displayed.

    You use the Advanced Display Filter for that.

    Assuming you are using Trados Studio 2022 and have version 3.1.0.6  of the plugin, can you tried this?

    Keen to hear from you

    Lyds

    Lydia Simplicio | 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

    emoji