SDL have not created new filetypes for these formats because they are really too old, and probably too little used to warrant the development effort in trying to support them directly in the new tools. You can launch the appropriate S-Tagger application from the File Menu and you’ll find the familiar applications to create your TTX files here. You will still need to convert these to TTX using S-Tagger… but the good news is that this has been built into Studio so you don’t need Trados installed to be able to do this. Phew… I think that’s about it, and the question that arises now is can we now live without Trados, or do we still need it to be able to do any of these things? Well let’s see… and we’ll start off with what’s covered in Studio itself, and I am going to be referring to the latest Studio 2014 version.
You needed to prepare your files as TTX or Bilingual DOC so your colleagues who were still using older tools could share the work with you.You received files that your client asked you to convert to TTX or Bilingual DOC for them.You received Bilingual DOC files for Translation.
You received unsegmented TTX files and you needed to fully segment them to ensure compatibility when the translated TTX was sent back.Trados can convert these to TTX using S-Tagger. You received FrameMaker 7, or Interleaf/QuickSilver files for translation.
#Winalign trados 2011 how to
I also think that the number requiring this as a proportion of the entire userbase is somewhat smaller than the various social media outlets would have us believe, and this is probably because historically the Trados user forums have been around a lot longer so these users know where to go for help, and as the new tools have been introduced the question of how to deal with these legacy workflows has been a common theme.īut what were the reasons you needed Trados for after Studio was first launched and can we really do without it now?
I don’t think this will come as a surprise to anyone as SDL had already ceased to support SDL Trados 2007 since the end of 2012, and with the releases of the 2009, 2011 and now 2014 versions of SDL Trados Studio it’s inevitable that the 2007 Suite version will follow suit.īut what does this really mean? Can we live without SDL Trados 2007? (I’m going to refer to these products separately as Trados and Studio for clarity and brevity.) I think many users have been happily living without it for some years now, and only those who are exposed to legacy workflows driven by the use of old filetypes or Trados customised business processes experience the problems this can present. The launch of SDL Trados Studio 2014 this month brings with it the news that SDL Trados 2007 Suite will no longer be supported from the end of this year.
0 kommentar(er)
