Not Considering

File Types: when importing settings they are placed 2nd

Dear community,

 

I would like to make sure our project managers use the right file type

 

Our technical team creates trados settings for them

 

when they import them into trados, all are checked, and those imported replace the existing ones. Nevertheless, if the same format has more than one file type, Trados will take into account the first in the list.

 

EXAMPLE:

Word 2013 file type

Word 2016 file type

Word 2003 file type

 

My technical team sends a setting for 2016. My project manager correctly imports it BUT as 2013 is above it Trados will not recognize the right one.

 

Could you either:

- when a setting is imported deactivate the rest of them but SDLXLIFF ?

- when a setting is imported automatically place it just below SDLXLIFF ?

 

Thanks in advance,

Clara

Clara Ginovart

  • The thing is that you are supposed to RENAME your customized file type in the first place!

    Then it not only won't overwrite the built-in definition, but more importantly clearly show that it's DIFFERENT FROM THE DEFAULT ONE and thus prevent confusions like "But I used Word 2016 setting, look! Well, yes, but it's not 'our' Word 2016 setting..."

    And THIS is the CORE of the problem which must be solved... not the consequence you are proposing.