| Pages in topic: < [1 2] | Poor old Trados! Thread poster: MartinPorto
|
|---|
| From Trados to SDL Tradosand back to Trados | Aug 3, 2012 |
[quote]Pavel Tsvetkov wrote:
Jabberwock wrote:
As you said, translators should not be required to be IT specialists. If I install ten packages on my "poorly configured" system and out of the ten only one consistently crashes with no apparent reason, then it is natural that I will blame that one piece of poorly written software. The argument that Trados runs well on pristine systems is absurd. Software should be able to run on real systems - nobody will buy a separate computer just to run Trados...
When Trados was simply called just this, it was OK. The customer support was poor as it is now but the tool itself was practical and adaptable to any situation. When I was told I had to switch to SDL Trados because Trados 6 wouldn't work on Windows 7, I was to say the least extremely annoyed. Not only did I have to buy an expensive program but on top of this, it no longer did the tasks I needed to do.
SDL Trados seems to mostly target big companies with big projects to be translated line after line by robot-like translators who have no choice but to follow the document this way.
I attended online SDL Trados training and asked questions related to my personal requirements. I didn't get any good answer. In fact, at the end of the session, I was told in private that SDL Trados isn't meant to be used this way.
So what do I need that is so incredible? Well, simply what my old Trados 6 can do which is:
Working with MSWord and being able to have a full view of the document I'm working on.
Being able to produce bilingual files easily after having removed the Trados code. Most of my clients require this.
Being able to work with bilingual source files which need to be manually processed.
So I decided to wave goog bye to SDL Trados 2011 and to find a way to install my good old Trados 6 on Windows 7 since SDL Trados told me that I couldn't purchase SDL Trados 2009 (which works like the old Trados) without purchasing 2011 which was of no use to me whatsoever.
And bingo! My Trados 6 is now working fine with Windows 7 even though SDL Trados assured me that it wasn't possible at all.
Well, sometimes it's best not to follow advice from a company which is afterall, simply trying to sell its products.
Last but not least, I had constant problems with SDL Trados (2009&2011). It was a server-based version and for some reason the license wouldn't register. It took forever to get an SDL Trados technician to help. In the meantime, I couldn't use Trados for my work at all and I lost quite a few contracts during those 3 to 4 weeks during which I had to wait for technical help. SDL Trados couldn't find anything wrong so what they did was to send me the usual info about how to set-up SDL Trados. This info was completely useless to me since I had already installed it as it should be.
Eventually it seems that they realised that the problem was coming from their end. They never stated so as such but it started working...by magic.
I'm happy with my old Trados, I can do what I please. I don't even SDL Trados 2011 to process my PDF files etc for me. I can do it myself with editable text. This might have been the only function that I appreciated about SDL Trados 2011. But on the whole I disliked immensely the software set-up, the lack of options for the work I need to know and the poor visibility of the overall document with far too many info all over the place. My old Trados 6 is not a problem for my regular agencies, they send me the right Trados format and that's that.
| | | | Emma Goldsmith 
Spain
Local time: 14:05
Member (2004)
Spanish to English
| There's no accounting for tastes! | Aug 3, 2012 |
Valerie Marzac wrote:
I'm happy with my old Trados, I can do what I please.
It's great to hear that you're happy with Trados 6 and that you've got it up and running on Windows 7.
Unlike you, I'm happy with Trados 2011. There are so many features that make it much more productive that Workbench, and exciting new ones have been added in the latest SP2 release, which I discussed here: http://traductormedicina.wordpress.com/2012/07/18/sp2/
I personally wouldn't dream of going back to "good old Trados 6", but then there's no accounting for tastes. 
| | | | | Bugs, but largely bad features | Aug 17, 2012 |
My gripe with Trados is not so much about the bugs, it is largely about inexplicable design decisions and just plain bad design.
With Trados I can't really see much progress from one version to another, because for one good feature SDL adds they create some problems somewhere else.
For example, the language variations in TMs are an incredible pain in the behind.
I can't work on a SDLXLIFF or TTX designated "UK English" (by the client) with a "US English" TM.
As a result,... See more My gripe with Trados is not so much about the bugs, it is largely about inexplicable design decisions and just plain bad design.
With Trados I can't really see much progress from one version to another, because for one good feature SDL adds they create some problems somewhere else.
For example, the language variations in TMs are an incredible pain in the behind.
I can't work on a SDLXLIFF or TTX designated "UK English" (by the client) with a "US English" TM.
As a result, I often have to export my TM and reimport it as a different language variant.
I understand that SDL has some kind of reasoning for keeping this language variant requirement, but I don't care. For me, it's just an incredible annoyance that costs me a considerable amount of time and thus money. This is an entirely artificial problem that SDL has created and refuses to address.
There are a variety of other issues with Studio, such as the fact that you just usually need way too many clicks to accomplish something.
As an example, say you want to analyze the file you are working on (possibly to see how much of the untranslated text are fuzzy matches). You need a total of 9 clicks, minimum, to make the report and get to the report. The process is not streamlined at all, and that is just true for so much in Studio.
But the real clincher for me, the one that reveals what kind of a company SDL is, is that Studio STILL has no autosave feature.
That is mind-boggling, and inexcusable.
There is only one explanation for this:
The people responsible at SDL are incompetent.
So I don't really have much hope that Studio will ever become anything more than the clunky, semi-improvised patchwork that it is.
[Edited at 2012-08-17 19:42 GMT]
[Edited at 2012-08-17 19:42 GMT] ▲ Collapse
| | | | | Not so incomptent! | Aug 19, 2012 |
While I heartily agree with the comments made by Henning above, I strongly object to his statement
"The people responsible at SDL are incompetent. "
What I note in these forums is that the majority of complaints here relate to older versions of the software, some of them going back to 2007. We all know that technology has made great advances and even Windows 7 is soon going to be outdated.
But Trados has been consistently providing support for its earlier versions... See more While I heartily agree with the comments made by Henning above, I strongly object to his statement
"The people responsible at SDL are incompetent. "
What I note in these forums is that the majority of complaints here relate to older versions of the software, some of them going back to 2007. We all know that technology has made great advances and even Windows 7 is soon going to be outdated.
But Trados has been consistently providing support for its earlier versions, you can still get help, updates on things like Tag Editor, I don't even know what it is, while I have a fairly good grip on SP2.
So, according to me, the problem with Trados is not that of being incompetent but rather, it is one of trying to do too much. In some twisted corporate logic, it is perhaps forced to do so if only in order to maintain its market share.
Vishwa
Dehradun
India ▲ Collapse
| | |
|
|
|
Vishwa,
I understand what you mean with SDL trying to do too much, and I am sure that is part of the problem (it probably accounts for the lack of streamlining and the many clicks you need to get something done). However, the problems go much deeper.
There's just no excuse for the fact that Studio 2011 STILL has no autosave.
This function is both OBVIOUSLY vital (like a seatbelt) as well as easy to implement.
Other than incompetence, I can see no reason why it woul... See more Vishwa,
I understand what you mean with SDL trying to do too much, and I am sure that is part of the problem (it probably accounts for the lack of streamlining and the many clicks you need to get something done). However, the problems go much deeper.
There's just no excuse for the fact that Studio 2011 STILL has no autosave.
This function is both OBVIOUSLY vital (like a seatbelt) as well as easy to implement.
Other than incompetence, I can see no reason why it wouldn't be implemented.
I guess the major theme, in looking at Trados 2007 and Studio 2011, is the following:
Workbench 2007 is a product with limited functionality and some bugs, which does what it does reasonably well. As a user, I feel good about it.
Studio 2011 has a much greater functionality (many more bugs as well), which does what it does reasonably well. However, as a user, it frequently drives me crazy.
I can understand lack of functions. I can understand bugs. What annoys me greatly is when developers create artificial problems for me. The TM language variant is maybe the best example.
There's been a lot of criticism of SDL's decision to enforce language variants, because it is a major annoyance. SDL has given its reasoning, and it clearly doesn't hold water.
I don't care about optimizing leverage, what I *do* care about is actually being able to work with my TM and the files my clients give me.
As many have said before, there should be the possibility of overriding it directly in the program, rather than having to export and import the TM and overriding it that way.
It is BS like this that now has me researching alternatives CAT tools. I really, really don't want to invest the time required to do so, but I am also increasingly annoyed at SDL and (importantly!) it seems like they are absolutely unwilling to change their minds on some critical and much criticized design decisions.
SDL is apparently unwilling to revisit design decisions, no matter how boneheaded they are.
That is incompetence.
[Edited at 2012-08-20 02:10 GMT] ▲ Collapse
| | | | Alex Lilo
Local time: 15:05
English to Russian
+ ...
| Term recognition is still (!) very flaky | Jul 2, 2013 |
Atso Puronen wrote:
...
Term recognition is still (!) very flaky
...
My experience is that term recognition is even worse in TS2011. 2009 seemed to handle terms better.
| | | | | Not so Poor Old Trados | Jul 3, 2013 |
Alex Lilo wrote: Atso Puronen wrote:
...
Term recognition is still (!) very flaky
...
My experience is that term recognition is even worse in TS2011. 2009 seemed to handle terms better.
Try this -> TermInjector (OpenExchange) - should change your mind: http://s1360.photobucket.com/user/blieber45/slideshow/?sort=3
Not a single keystroke, except for Ctrl+T with just an Exact Match/Regular Rule File - can't beat that, 0% is the default value in TermInjector - I didn't change it.
Cheers,
Bernard
[Edited at 2013-07-03 21:42 GMT]
| | | | Mpoma
United Kingdom
Local time: 13:05
French to English
| Trial by Ordeal | Sep 28, 2014 |
What we (translators) really need is a decent open-source project covering the most basic and common tasks, and doing it well. (Incidentally, we also need an open-source project for dictation).
Not only would this then mean that we could examine the code (and improve it), but it would also mean we could finally leave behind the dreadful proprietary OSs and move entirely to Linux.
I'm aware of OmegaT but have always found it lamentable... trying to throw a TM of 100 MB ... See more What we (translators) really need is a decent open-source project covering the most basic and common tasks, and doing it well. (Incidentally, we also need an open-source project for dictation).
Not only would this then mean that we could examine the code (and improve it), but it would also mean we could finally leave behind the dreadful proprietary OSs and move entirely to Linux.
I'm aware of OmegaT but have always found it lamentable... trying to throw a TM of 100 MB at it it just seems to die, in my experience. Presumably it's not designed for that purpose. But I also examined some of its code at some point and found the basic faith in "Levenstein distance" rather naive.
I have actually bought SDL Trados 2014 Studio and the latest M$ Office suite... but only because clients (bless 'em) are reassured by ownership of such products. In fact technical wizardry, conversion of one incompatible format to another (TMX, Word, etc.) is all part of the fun: fail to get on top of this stuff and you are sooner or later going to get a job you simply can't do. Add to that knowledge of Unicode, etc. I often choose to work in Trados 6.5, although that is also rubbish, to the extent of actually failing to do (it seems) precisely what it was meant to do: i.e. colour-code all the differences between a given TM seg and a new seg (for the record: this is my opinion).
I regard this "conversion knowledge" as something akin to the barriers to the Medieval Guilds, only much more secure. Face it, the nerds are already inheriting the Earth. In many ways translators who do come through such Trials by Ordeal are lucky to end up as part of the Geekocracy. ▲ Collapse
| | |
|
|
|
A. da Silva
Japan
Local time: 21:05
Portuguese to English
+ ...
| Bad customer service | Dec 3, 2014 |
I just need to mention how I've had mostly negative experiences with SDL so far. I've to work with Trados, which is fine for the most part, and I had to call sales and customer service yesterday. Support is a very expensive little feature and yet the people on the phone were anything but helpful. In fact, the support rep was downright condescending.
[Edited at 2014-12-04 10:27 GMT]
| | | | | I don't think this is typical... | Dec 4, 2014 |
Ana da Silva wrote:
I just need to mention how I've had mostly negative experiences with SDL so far. I've to work with Trados, which is fine for the most part, and I had to call sales and customer service yesterday. Support is a very expensive little feature and yet the people on the phone were anything but helpful. In fact, the support rep was downright condescending.
[Edited at 2014-12-04 10:27 GMT]
... and am sorry you had this experience. I don't know where you went for help or who you spoke to but if you still need assistance or would like to talk to someone about your experience I'd be happy to help?
There are many ways to get in contact with us these days, with or without a support contract, and often the worst experiences come through not using the most appropriate way and you end up talking to someone who really can't help you. Ideally all SDL employees would ensure you were directed to the right place but realistically this is unlikely to happen all of the time.
Please drop me an email if you still need assistance.
Regards
Paul
[email protected]
| | | | A. da Silva
Japan
Local time: 21:05
Portuguese to English
+ ...
| Thanks but if I can help it, no, thanks. | Dec 5, 2014 |
SDL Support wrote: Ana da Silva wrote:
I just need to mention how I've had mostly negative experiences with SDL so far. I've to work with Trados, which is fine for the most part, and I had to call sales and customer service yesterday. Support is a very expensive little feature and yet the people on the phone were anything but helpful. In fact, the support rep was downright condescending.
[Edited at 2014-12-04 10:27 GMT] ... and am sorry you had this experience. I don't know where you went for help or who you spoke to but if you still need assistance or would like to talk to someone about your experience I'd be happy to help? There are many ways to get in contact with us these days, with or without a support contract, and often the worst experiences come through not using the most appropriate way and you end up talking to someone who really can't help you. Ideally all SDL employees would ensure you were directed to the right place but realistically this is unlikely to happen all of the time. Please drop me an email if you still need assistance. Regards Paul [email protected]
Thanks for your reply, Paul, but the facts that it's work just to find a phone number on your site and that 3/3 people were that unhelpful on the phone do not make me want to do business with your company.
I even left my contact info with one of your reps but I still haven't heard back - and as far as I know the service I'm looking to buy is rather pricey, not that it should make a difference. (Btw, I did contact a 4th person at your company about my bad experience but they're only keen on getting all my personal details - for what? - and don't seem to care about what actually happened). One of your reps actually kept trying to talk me out of the service I want because "it's very expensive," he said over and over again. I mean, what kind of people do you people hire over there...
SDL at the moment is my last resort, even after another big company I really would rather not work with. If I really can't find another solution then I'll contact you.
[Edited at 2014-12-05 12:27 GMT]
| | | | Dominic D.
Local time: 14:05
Serbian to Russian
+ ...
Studio 2019 doesn't even offer properly working Word preview anymore. It lags and crashes all the time. Wouldn't buy again.
| | | | | Pages in topic: < [1 2] | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Poor old Trados! | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
| | TM-Town | Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
