![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Well, it took me a little while to get myself moving this morning. First, I had to edit the NASA document and send it off to the editor. Along the way, I ended up looking for a radiogram from January, which I suspected would help me resolve a terminology issue. I didn't find the thing, so I sent my best educated guess.
I then sat down and immediately wrote an invoice for the job, and faxed it off.
When I finally got down to the nuclear work, I'd divided the 34 remaining pages into three batches of 11, 11, and 12 pages, respectively. Assuming I do a batch a day, that'd give me all of Wednesday to massage/edit/review, etc.
I got today's share done in about 5 hours, and did a couple of pages of tomorrow's work, too, so I'm going to reshuffle what's left when I sit down to work tomorrow. The document is still on track to weigh in at about 20K words.
* * * I'd been thinking of writing a Perl script to process the data for the dropoff packages that we scan at the store. Properly submitted, the store collects a couple of hundred dollars a month from UPS for handing the packages. Unfortunately, the application that I wrote using C++ Builder isn't bug free.
First of all, the date routines that work fine on a "pure" Windows box seem to not work so well when run on a box running Windows on top of Win4Lin. In short, I end up with strange-looking dates.
Second, sometimes the data coming in off the scanner is not properly interpreted, leaving "extra" characters in the scanned data. (I've since learned that the "extra" characters represent data that for some reason remains embedded in the scanned string as a three-digit decimal ASCII value of the character that should be there, i.e., the string '23456' might end up looking like '2305256', where '052' should be '4'.)
I just spent some little time with C++ Builder, chasing down some package variables that I suspect do not exist. The app works okay on my desktop, which is why I suspect the problem with the date is associated with running on top of a Linux OS.
Anyway, I sat down with what the report ought to look like and wrote two Perl scripts to help process the data. Now, having gone through the raw data to fix ill-formed dates, I run the data through the first script to obtain the proper format. Then, after going through the processed data to fix the "extra" characters, I run the data through the second script, which actually generates the report. The only thing I have to do after running the second script is make sure the spacing is correct on the last two lines of the report, where I state how much the report is worth.
* * * I'm going to have to get some good rest tonight, since we all are going to have to be at the store in the morning, so Galina can drive to Durango and pick up boxes. (We are hoping that the delivery driver will be out delivering tomorrow.) Drew is supposed to be back Tuesday.
I can't wait.
Cheers...
I then sat down and immediately wrote an invoice for the job, and faxed it off.
When I finally got down to the nuclear work, I'd divided the 34 remaining pages into three batches of 11, 11, and 12 pages, respectively. Assuming I do a batch a day, that'd give me all of Wednesday to massage/edit/review, etc.
I got today's share done in about 5 hours, and did a couple of pages of tomorrow's work, too, so I'm going to reshuffle what's left when I sit down to work tomorrow. The document is still on track to weigh in at about 20K words.
First of all, the date routines that work fine on a "pure" Windows box seem to not work so well when run on a box running Windows on top of Win4Lin. In short, I end up with strange-looking dates.
Second, sometimes the data coming in off the scanner is not properly interpreted, leaving "extra" characters in the scanned data. (I've since learned that the "extra" characters represent data that for some reason remains embedded in the scanned string as a three-digit decimal ASCII value of the character that should be there, i.e., the string '23456' might end up looking like '2305256', where '052' should be '4'.)
I just spent some little time with C++ Builder, chasing down some package variables that I suspect do not exist. The app works okay on my desktop, which is why I suspect the problem with the date is associated with running on top of a Linux OS.
Anyway, I sat down with what the report ought to look like and wrote two Perl scripts to help process the data. Now, having gone through the raw data to fix ill-formed dates, I run the data through the first script to obtain the proper format. Then, after going through the processed data to fix the "extra" characters, I run the data through the second script, which actually generates the report. The only thing I have to do after running the second script is make sure the spacing is correct on the last two lines of the report, where I state how much the report is worth.
I can't wait.
Cheers...
