Nearly a perfect storm of suck...
Aug. 14th, 2009 01:53 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpIt is, of course, a cardinal sin to leave things until the last minute, and in fact, the fact I'm writing this about a job due Tuesday is evidence of my not having done so, but things did get dicey for a while, there.
Last night, I launched Wordfast Pro, which is slated to be the next generation of the product upon which I base quite a bit of my income. The idea was to use it to translate a Web site that is the object of my current attention, and for that purpose, I can - without reservation - say that the application is "not ready for prime time."
I strongly suspect the show-stopper is the fact that the Web site has been composed using the 'windows-1251' character set, while Wordfast Pro seems only capable (no matter what the settings say) of understanding the 'utf-8' character set.
It was difficult to find information on the Internet about this subject, because starting around 9 pm last night, the DNS provided by my ISP - which is the service that converts human-readable web site names into strings of network addresses - apparently had a partial nervous breakdown.
I say partial because I could get at some sites, but not others. Naturally, all the sites I wanted to get to were shut off to me, so I had to go to plan B and connect to the Internet via my Verizon BlackBerry.
Anyway, I'm back doing things the old fashioned way, using Wordfast "Classic," and I'm hoping I'm at least 1/3 of the way through the job. There are other small jobs that need attention, too, and I better get to them.
Cheers...
Last night, I launched Wordfast Pro, which is slated to be the next generation of the product upon which I base quite a bit of my income. The idea was to use it to translate a Web site that is the object of my current attention, and for that purpose, I can - without reservation - say that the application is "not ready for prime time."
I strongly suspect the show-stopper is the fact that the Web site has been composed using the 'windows-1251' character set, while Wordfast Pro seems only capable (no matter what the settings say) of understanding the 'utf-8' character set.
It was difficult to find information on the Internet about this subject, because starting around 9 pm last night, the DNS provided by my ISP - which is the service that converts human-readable web site names into strings of network addresses - apparently had a partial nervous breakdown.
I say partial because I could get at some sites, but not others. Naturally, all the sites I wanted to get to were shut off to me, so I had to go to plan B and connect to the Internet via my Verizon BlackBerry.
Anyway, I'm back doing things the old fashioned way, using Wordfast "Classic," and I'm hoping I'm at least 1/3 of the way through the job. There are other small jobs that need attention, too, and I better get to them.
Cheers...
