How to set QA checker to check the Header length limitation in Word?

I am trying to get the QA checker to count the characters in a header. I have set the target length and that I want to check this is header only. I have tried with "Header" and "H" (which I think are the contexts) without any success. 

I did not find an option to set the lenth limiation in the file type settings (Microsoft Word). Any ideas how to make it work?

Trados Studio QA Checker 3.0 Length Verification settings window showing options for checking length limitation with 'Check the following contexts only' selected and 'H' entered as the context.



Generated Image Alt-Text
[edited by: Trados AI at 1:41 PM (GMT 0) on 29 Feb 2024]
emoji
Parents
  •   

    I believe the proper way to use this is to provide the "Location" and not the "Code".  So you would write:

    Header
    Paragraph
    Subtitle
    List item
    etc.

    However, I can't actually make this work either in Trados Studio 2022, 2021, 2019, 2017.  I checked the bug database and can find an unresolved bug from when we moved to the new Word filetype (LTB-1316) and a comment it still fails in 2017.  So I think this must have been broken when we first moved to the new DOCX filetype and it's never been fixed... and never been reported since.  As a result the priority has probably always been low.

    I logged this again for the current version of Trados Studio under our reference CRQ-37134.

    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

    emoji
Reply
  •   

    I believe the proper way to use this is to provide the "Location" and not the "Code".  So you would write:

    Header
    Paragraph
    Subtitle
    List item
    etc.

    However, I can't actually make this work either in Trados Studio 2022, 2021, 2019, 2017.  I checked the bug database and can find an unresolved bug from when we moved to the new Word filetype (LTB-1316) and a comment it still fails in 2017.  So I think this must have been broken when we first moved to the new DOCX filetype and it's never been fixed... and never been reported since.  As a result the priority has probably always been low.

    I logged this again for the current version of Trados Studio under our reference CRQ-37134.

    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

    emoji
Children
No Data