May. 29th, 2016

alexpgp: (Default)
I love it when a password that I've written down is rejected. I mean, who knows? Maybe I didn't write it down correctly, right?

So I ask for a password reset, jumping through the requisite hoops, and eventually get an email, and eventually get to the part where I specify a new password, and then—when I use the password that I've written down (I am an intrinsically lazy sob)—the system responds with a message to the effect that I can't use my existing password!

The mind... boggles.

Grrr.
alexpgp: (Visa)
For some reason, somehow, MemoQ apparently did not shut down correctly, or at any rate, an XML file associated with a project I was working on yesterday morning became corrupted, so that attempting to open the project this morning netted me an error message and headache.

The upshot was that I could not get at the work I'd done yesterday, which meant I either had to do the work from scratch or figure out a way to get MemoQ to cough it up.

Normally—assuming such a concept applies at all in this context—one would recover by restoring a backup of the project, except that projects are not backed up automatically (which means you've got to deliberately back them up yourself), and as it may very well be the case that the problem was caused by MemoQ failing to exit gracefully, I would not have a backup available even if I were in the habit of routinely making backups.

Surprisingly, the Internet was not much help here. The one page that provided a straightworward fix apparently no longer applied, as the offered advice instructed me to go to a particular directory and delete a particular file. The directory was there; the file was not.

No matter. As it stands right now, I "solved" the problem by creating a "new" project that uses the same terminology and translation databases as the old one. I then "imported" the file I was last working on, as if I was getting ready to only start working on it, and then ran a feature called "pretranslate," which compares the segments in the newly imported file against entries in the translation memory.

Fortunately, the importation process resulted in a pretty good set of segments that required no "splittling" or "joining" of segments, so the "pretranslate" operation resulted is a file that is almost completely translated. The exceptions were segments that I left as "questionable" yesterday and consequently, not saved to the translation memory.

'Tis a small price.

Meanwhile, I've put three racks of baby back ribs on the grill in the back yard.

It's going to be an interesting Sunday.

Cheers...

Profile

alexpgp: (Default)
alexpgp

January 2018

S M T W T F S
  1 2 3456
7 8910111213
14 15 16 17181920
21222324252627
28293031   

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Aug. 14th, 2025 02:05 am
Powered by Dreamwidth Studios