Brute force...
Feb. 27th, 2015 10:54 pmSo there I was, minding my own business, translating a document using MemoQ when something on my system—something that my gut tells me was either the Firefox browser or something to do with it—began to degrade the performance of my system to the point where the clock stopped and the computer became unresponsive.
Upon powering off, waiting for the hard drive to spin down, and then powering back up, running MemoQ resulted in no projects getting loaded. I eventually tumbled to the fact that I could open individual projects, but not the one I was working on when my system went belly up.
This annoyed me, because I was something like 70% of the way through the document I was working on, which also happened to be one of those "gee, this fell through the cracks" documents that suddenly became a rush this morning.
After spinning my wheels for about 20 minutes to no effect, I took the step of creating a new project (with a rather offensive name, as I was in a rather dark mood), adding the document I had been working on, specifying the translation memory file I had been using, and then initiating the application's "auto translate" feature. The good news was that because the original document had segmented cleanly (meaning I didn't have to join or split any of the segments created by the program), auto-translate basically filled in the translations I had written before my computer crashed in less time that it has taken me to type out the last dozen words of this sentence.
MemoQ than warned me, once I picked up where I had left off, that the translation memory file was corrupt, but I was able to fix that and then—thank goodness—finish the translation.
That said, the whole experience sort of burned away a lot of my energy, and I repaired to my bed to get some rest.
Additional assignments await my attention over the weekend, but it's still going to be a thin month, invoice-wise.
Cheers...
Upon powering off, waiting for the hard drive to spin down, and then powering back up, running MemoQ resulted in no projects getting loaded. I eventually tumbled to the fact that I could open individual projects, but not the one I was working on when my system went belly up.
This annoyed me, because I was something like 70% of the way through the document I was working on, which also happened to be one of those "gee, this fell through the cracks" documents that suddenly became a rush this morning.
After spinning my wheels for about 20 minutes to no effect, I took the step of creating a new project (with a rather offensive name, as I was in a rather dark mood), adding the document I had been working on, specifying the translation memory file I had been using, and then initiating the application's "auto translate" feature. The good news was that because the original document had segmented cleanly (meaning I didn't have to join or split any of the segments created by the program), auto-translate basically filled in the translations I had written before my computer crashed in less time that it has taken me to type out the last dozen words of this sentence.
MemoQ than warned me, once I picked up where I had left off, that the translation memory file was corrupt, but I was able to fix that and then—thank goodness—finish the translation.
That said, the whole experience sort of burned away a lot of my energy, and I repaired to my bed to get some rest.
Additional assignments await my attention over the weekend, but it's still going to be a thin month, invoice-wise.
Cheers...