ProZ.com global directory of translation services
 The translation workplace
Ideas

 
User
Thread poster: Tom Fennell
Trados Studio emergency

Tom Fennell
United States
Local time: 11:58
Russian to English
+ ...
Nov 29, 2009

I am just finishing up a 20,000 word project, and disaster struck.

Studio was slow, and I decided to restart. It "hung" when closing.

When starting again, I get the following message when I try to open my project, I get the following message:

Failed to activate project '1028 -1 - LL- Accounting Documents': Failed to load project from 'C:\Users\Tom\Documents\SDLTrados Studio\Projects\1028 -1 - LL- Accounting Documents\1028 -1 -LL- Accounting Documents.sdlproj': There is an error in XML document (109, 223). Unexpected end of file has occurred, The following elements are not closed: FileVersions, LanguageFile, LanguageFiles, ProjectFile, ProjectFiles, Project. Line 109, position 223.


Worse, I have no idea how to try to restore the project - the files are just sitting there, but all I can find are Russian-only .sdlxliff files - the English side seems to have disappeared.


HELP!!!!!


Direct link Reply with quote
 

Gillian Searl  Identity Verified
United Kingdom
Local time: 17:58
Member (2004)
German to English
start again Nov 29, 2009

Surely it's all in the TM, right? So create a new project with the clean source file and use the TM to translate. Does that help?

Direct link Reply with quote
 

Tom Fennell
United States
Local time: 11:58
Russian to English
+ ...
TOPIC STARTER
The Horror Deepens Nov 29, 2009


Gillian Searl wrote:

Surely it's all in the TM, right? So create a new project with the clean source file and use the TM to translate. Does that help?


More Studio wonders.

I rested assured that my TM was updating. It was a very repetitive set of files, and the segments were all being populated from TM from one document to the other (not within the document).

However, when I filter the TM, only the first, smallest file of 20 seems to be in the TM.

Trados HORROR! I think I've lost a week of work.

=======

UPDATE

after searching the whole disk, I found the project memory tucked inside the project folder.

Hallelujah!


========

UPDATE 2

Found the project Translation Memory and was able to recover 5564 of 6166 sentences (13,698 of 17,462 words).

Still....having to retranslate 601 sentences (9.75%) @#$!!!!!! 3763 words could be a day's work! $@@*$!!!

And deadline is 50 minutes from now!

Also, all of my corrections from the review stage seem to have been lost. I thought TM was being updated by review!




[Edited at 2009-11-29 17:08 GMT]

[Edited at 2009-11-29 17:10 GMT]

[Edited at 2009-11-29 17:11 GMT]


Direct link Reply with quote
 

Richard Bartholomew  Identity Verified
Germany
Local time: 18:58
Member (2007)
German to English
And all this for how much? Nov 30, 2009

Adding insult to injury, Trados costs a small fortune relative to, say, WordFast. It is also significantly more difficult to use. I hope that any advantages it has over simpler, cheaper systems are very considerable indeed. I have never experienced any problems even approaching those described here while using WordFast.

This just serves to confirm my attitude that simplicity is best (KISS principle). Trados has all the earmarks of a solution looking for a problem.


Direct link Reply with quote
 

Stanislav Pokorny  Identity Verified
Czech Republic
Local time: 18:58
Member (2009)
English to Czech
+ ...
Sure Nov 30, 2009


Richard Bartholomew wrote:

Adding insult to injury, Trados costs a small fortune relative to, say, WordFast. It is also significantly more difficult to use. I hope that any advantages it has over simpler, cheaper systems are very considerable indeed. I have never experienced any problems even approaching those described here while using WordFast.

This just serves to confirm my attitude that simplicity is best (KISS principle). Trados has all the earmarks of a solution looking for a problem.


Certainly, especially if you don't know how to use it. But that holds true for any production software.


Direct link Reply with quote
 

Grzegorz Gryc  Identity Verified
Poland
Local time: 18:58
French to Polish
+ ...
Attention :) Nov 30, 2009


Richard Bartholomew wrote:

Adding insult to injury, Trados costs a small fortune relative to, say, WordFast. It is also significantly more difficult to use. I hope that any advantages it has over simpler, cheaper systems are very considerable indeed. I have never experienced any problems even approaching those described here while using WordFast.

This just serves to confirm my attitude that simplicity is best (KISS principle). Trados has all the earmarks of a solution looking for a problem.

Don't attack SDL here, the thread may be closed by the staff...

http://www.proz.com/forum/software_applications/151708-misleading_advert_34501_words_translated_in_10_hours_by_only_one_translator-page5.html

Cheers
GG


Direct link Reply with quote
 

Maciek Drobka  Identity Verified
Poland
Local time: 18:58
Member (2006)
English to Polish
+ ...
OT: They DID finally close it, didn't they? Nov 30, 2009


Grzegorz Gryc wrote:


Don't attack SDL here, the thread may be closed by the staff...

http://www.proz.com/forum/software_applications/151708-misleading_advert_34501_words_translated_in_10_hours_by_only_one_translator-page5.html

Cheers
GG[/quote]

I followed the other thread closely for a few days, and to tell the truth, was surprised it was allowed to run for so long. I thought that maybe the site staff had adopted a more liberal, or should I say, more commonsensical attitude, and was pleasently surprised.

But no, it never fails, Big B. is there.

It's like a reflex. Whenever an important toe is stepped on, topics get squashed.

It's sad to see PC getting in the way of free exchange of thought.

Maciek


Direct link Reply with quote
 

Tom Fennell
United States
Local time: 11:58
Russian to English
+ ...
TOPIC STARTER
Update 3 Dec 6, 2009

Well after the whole thing was over, and after another 6 hour "disaster" on Thursday, I am better off.

Fun being on the "bleeding edge" of technology implementation.

I could have recovered my original work a different way, and lost only 2-3 hours from the corruption of my original file.

The root problem is non-functional Russian abbreviation list, leading to bad segmentation. Bad segmentation leads to much manual re-segmentation, leading to file corruption, leading to CRASH.

The base abbreviation list problem was submitted to SDL help desk 10 days ago, no response yet.

As for the rest, what can I say.

1. Studio has amazing, benefits due to ability to employ multiple termbases and memories.

2. This comes at the price of a very complex data structure. There are multiple bilingual files (now .sldxliff) and a project memory in addition to file-based memories that only gets updated when you tell Studio to update them. I went to a one day course in NYC at the ATA, and the complexity of the data structure was never mentioned, despite the fact that one can hardly call this an "advanced" or even "intermediate" item.

3. I've been to 2-day Wordfast training to evaluate it. Studio is definitely a level above, but you'd better either invest the time in self-training or a course before plunging into production use.


Direct link Reply with quote
 

Tom Fennell
United States
Local time: 11:58
Russian to English
+ ...
TOPIC STARTER
No, it wasn't actually yet in the "real" TM Dec 6, 2009


Gillian Searl wrote:

Surely it's all in the TM, right? So create a new project with the clean source file and use the TM to translate. Does that help?


That's pre-Studio TRADOS talk.

As I found out hours into another crash, Studio has a "project TM" that doesn't update the file-based TM's until it is told to. This means pre-translation won't work until after you have updated from project TM. Segment-by-segment translation replication works from project TM, but not the much faster pre-translation.


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Natalie[Call to this topic]
Maya Gorgoshidze[Call to this topic]

You can also contact site staff by submitting a support request »