Forum: SDL Trados support
Topic: Why do people still refuse Studio 2009 and later and stick with Tag Editor?
Poster: PapagenoX
Post title: TagEditor is way more intuitive
I'll tell you why a lot of people still prefer to use TagEditor-- because it's about 1000 times more intuitive!
Case in point: at my company (a translation customer in the main--I am one of those "rare as hen's teeth" internal translators) we have all of our documentation in SGML. Even after creating file types for Studio 2011 based on the old .ini files, which in turn were based on the DTDs for our document types (service manuals, maintenance manuals, service bulletins etc.) it's not an intuitive, easy thing to insert an sgml entity (a string which appears in text as a & followed by the entity name followed by a semicolon-- example & ordm ; --minus the spaces--which appears as º ) as a protected tag (I don't even think it's possible--the best I've been able to do is set it up as a plain text quick insert in the file type.
In 2007's TagEditor, no special preparation was required--you just went up to the Edit menu and there it was: insert entity--which let you insert AS A PROTECTED TAG in the editor anything that was in your .ini.
Another frustration I'm currently having with 2011 that was a breeze in TagEditor: how the heck to get tag pairs I've set up in the file type quick insert to actually show up in the editor when I insert them! A KEEP tag pair for instance, or an EMPH pair? I insert them and when I save target as I see them in the translation plain text, but when I'm still working in the file they don't appear on screen, even if I have tags set to show (and BTW 2011 doesn't remember my unchecking the "tags can be hidden" box in the quick insert editing window after I exit).
I'm sure that 2011 has all kinds of cool features if you run a translation agency, but as an actual translator, forget it, it's a pain, at least when working with SGML files. About the only cool thing I've found is that it autocompletes recognized terms from the termbase when you start typing them.
Topic: Why do people still refuse Studio 2009 and later and stick with Tag Editor?
Poster: PapagenoX
Post title: TagEditor is way more intuitive
I'll tell you why a lot of people still prefer to use TagEditor-- because it's about 1000 times more intuitive!
Case in point: at my company (a translation customer in the main--I am one of those "rare as hen's teeth" internal translators) we have all of our documentation in SGML. Even after creating file types for Studio 2011 based on the old .ini files, which in turn were based on the DTDs for our document types (service manuals, maintenance manuals, service bulletins etc.) it's not an intuitive, easy thing to insert an sgml entity (a string which appears in text as a & followed by the entity name followed by a semicolon-- example & ordm ; --minus the spaces--which appears as º ) as a protected tag (I don't even think it's possible--the best I've been able to do is set it up as a plain text quick insert in the file type.
In 2007's TagEditor, no special preparation was required--you just went up to the Edit menu and there it was: insert entity--which let you insert AS A PROTECTED TAG in the editor anything that was in your .ini.
Another frustration I'm currently having with 2011 that was a breeze in TagEditor: how the heck to get tag pairs I've set up in the file type quick insert to actually show up in the editor when I insert them! A KEEP tag pair for instance, or an EMPH pair? I insert them and when I save target as I see them in the translation plain text, but when I'm still working in the file they don't appear on screen, even if I have tags set to show (and BTW 2011 doesn't remember my unchecking the "tags can be hidden" box in the quick insert editing window after I exit).
I'm sure that 2011 has all kinds of cool features if you run a translation agency, but as an actual translator, forget it, it's a pain, at least when working with SGML files. About the only cool thing I've found is that it autocompletes recognized terms from the termbase when you start typing them.