• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 306 views
  • Users 0 members are here
Options
Related

Why do batch tasks hotkeys change from one project to another?

Antonio Jiménez Esteller

Hello,

I use Studio 2022 Pro.

I have noticed that batch tasks hotkeys change depending on the project selected. See:

Screenshot of Trados Studio 2022 Pro showing the batch tasks menu with various tasks listed, such as 'Pre-translate Files' and 'Verify Files'.              Another screenshot of Trados Studio 2022 Pro with the batch tasks menu, similar to the first image, indicating a consistent interface.

This happens in the Project view. If I go into File view, they do change again...

I understand that different projects may have different tasks available, but why do hotkeys need to change? What is the point of hotkeys if they are inconsistent from one project to another?

Is there a way of making hotkeys static and not dynamic?

Also, just for general info, I tried 2024 Pro, extremely buggy, a real disaster... really well spent 1k€. Since I installed and unistalled 2024, custom batch tasks do not work well in 2022 (I never got to make them work in 2024). Even if they do exist, they are not shown in the batch task menu anymore.

Thans in advancefor any help.

Cheers,

Antonio

Generated Image Alt-Text
[edited by: RWS Community AI at 9:35 AM (GMT 1) on 25 Jul 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

      

    That's the first time I have even seen anyone analyse these hotkeys!!

    So, I took a look and can conclude this based on my tests in 2024:

    Task Hotkey
    Finalize F
    Analyse Files A
    Apply Language Weaver Metadata P
    Apply PerfectMatch L
    Copy to Target Languages C (Only in the Projects View for Projects using Monolingual Source files)
    Create QE Report C1
    Export Files X
    Export for Bilingual Review E
    Generate target files (cloud projects) G (greyed)
    Generate Target Translations T
    GroupShare Analyse and Translate N (greyed)
    Populate Project Translation Memories R
    Pre-translate Files O
    Pre-translate Files with OpenAI provider for Trados S
    Pseudo-translate U1
    Translation Count I
    Translation Quality Assessment Q
    Update from Bilingual Review M
    Update from Reviewed Target File (Retrofit) D
    Update Main Translation Memories U2
    Update Project Translation Memories J
    Verify Files V
    WIP Report W1
    Word Count W2
    Custom C2
    Everything was consistent between the Projects View, Files View and Editor View with the exception of Copy to Target Languages which was only available if my project contains monolingual source files.  This kind of makes sense because bilingual files have already got a target language defined so this task is useless for these files.
    Can you identify the type of projects and sources files in them?
    Other than that all the hotkeys are consistent for me.

    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
  • 0

      

    That's the first time I have even seen anyone analyse these hotkeys!!

    So, I took a look and can conclude this based on my tests in 2024:

    Task Hotkey
    Finalize F
    Analyse Files A
    Apply Language Weaver Metadata P
    Apply PerfectMatch L
    Copy to Target Languages C (Only in the Projects View for Projects using Monolingual Source files)
    Create QE Report C1
    Export Files X
    Export for Bilingual Review E
    Generate target files (cloud projects) G (greyed)
    Generate Target Translations T
    GroupShare Analyse and Translate N (greyed)
    Populate Project Translation Memories R
    Pre-translate Files O
    Pre-translate Files with OpenAI provider for Trados S
    Pseudo-translate U1
    Translation Count I
    Translation Quality Assessment Q
    Update from Bilingual Review M
    Update from Reviewed Target File (Retrofit) D
    Update Main Translation Memories U2
    Update Project Translation Memories J
    Verify Files V
    WIP Report W1
    Word Count W2
    Custom C2
    Everything was consistent between the Projects View, Files View and Editor View with the exception of Copy to Target Languages which was only available if my project contains monolingual source files.  This kind of makes sense because bilingual files have already got a target language defined so this task is useless for these files.
    Can you identify the type of projects and sources files in them?
    Other than that all the hotkeys are consistent for me.

    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