Idea Delivered

https://appstore.rws.com/Plugin/257?tab=documentation 

Batch task for quick creation of Pseudo-translated Target files to be always found from the same local folder

Would be GREAT FUNCTION for pre-processing:

1) Batch task which does both with one click:

- pseudo-translates expanding target segments by 1,3 (using dollar signs to detect quicker and easier if something is not translated)
- creates a Target file always to the same location on your local folder

This makes it easy, efficient and quick to find and check the target file, it’s behaviour and functionalities included.


Screenshot of the Pseudo-translate settings in Trados, showing options to expand target segments by a factor of 1.3 and apply pseudo-translation using the dollar sign.

2) To improve efficiency, possibility to define in Translatability project template (and modify per translatability project if needed) always the same path to your local folder where Target Pseudo-translations are saved:

- no need to wait for Notifications
- no complex folder names
- pseudo-translations always to be found in the same place
- you can add Target folder to your Quick access folders in windows, where target files quickly accessible with one click

 Screenshot of a Windows Explorer window showing the folder path 'DATA (D:) > Translatability test > fr-FR' with the 'fr-FR' folder highlighted.

3) in general the possibility for pre-processing team to create own batch tasks for their own Translatability test projects, if they find that necessary

LEENA VALTARI
Parents

  • Thank you for your question 

    This idea is used in Studio and is a proposal for development for Cloud.

    Further information:

    This is what I use in my local Translatability project in Studio at the moment, and find it really practical and quick. After checking Tags in Studio, run batch task "Pseudo-translate + create Target file" and you find files always from the same place. They open very quick from local drive so it is quick to check what ever needed (easy with dollar signs to see if something is NOT translated). This provides flexibility for task creation according to preferences/needs. (to name few benefits of using local project)

    Important thing is that the Default Settings in Translatability test project are the same as in Groupshare projects (both are done based on a template). 

    If a change is needed in Default Settings, this is done to both at the same time: Groupshare templates and local Translatability test project template.

    Then when job comes, easy to check first in local project, if any settings need to be changed in GS project before publishing to translators.

    If something like this could be achieved in Cloud projects, it would be great

Comment

  • Thank you for your question 

    This idea is used in Studio and is a proposal for development for Cloud.

    Further information:

    This is what I use in my local Translatability project in Studio at the moment, and find it really practical and quick. After checking Tags in Studio, run batch task "Pseudo-translate + create Target file" and you find files always from the same place. They open very quick from local drive so it is quick to check what ever needed (easy with dollar signs to see if something is NOT translated). This provides flexibility for task creation according to preferences/needs. (to name few benefits of using local project)

    Important thing is that the Default Settings in Translatability test project are the same as in Groupshare projects (both are done based on a template). 

    If a change is needed in Default Settings, this is done to both at the same time: Groupshare templates and local Translatability test project template.

    Then when job comes, easy to check first in local project, if any settings need to be changed in GS project before publishing to translators.

    If something like this could be achieved in Cloud projects, it would be great

Children