07-06-2023, 09:42 AM
I go in on July 20 for an NRI with dye. Should know more after that.
DM, a lunch or something in August sounds good.
In putting together my collection of stories, I realized 2 predate having a computer file. So I flatbed-scanned one story from a book with sufficiently flexible spine, and I took photos of the pages of another book with a stiff spine while LCF pried it open. The result of both was a series of jpgs, one per page. I cleaned and straightened them in photoshop (maybe optional step), then uploaded the jpgs to google drive. There the magic happens. I select one of jpgs, right-click, and from the dropdown there's an OPEN WITH submenu. From that I choose Google Docs. After a few seconds of grinding, the jpg opens. But because I used Google Docs, beneath the jpg is a translation of the text in the jpg as actual text. I can copy and paste that into a Word doc.
As for voice to text, I've heard that for prose, Dragon isn't the best. Then again, I read that maybe 3 years ago, and I don't remember where. And this area is growing so fast. I tried using Microsoft's version 3 years ago, whatever it's called, and it kept bailing on me after a few words. Then I tried Google's version in Google docs, and it's nice--though it cuts out after a few paragaphs. My big problem at present is my handwriting. I'll jot paragaphs of revsisions in the margin of a story and decide it'd be faster to read it in than type it. But in voicing it, I'll hesitate a lot, because I can't read my own handwriting.
Fiction poses its own special problems for voice to text. Lots of long or unfamiliar or made-up words. Or strrange names like Kabita. So I'll just say K, but it still translates it differently each time--as K, or Kay, or Cay, or Kate, or Gay. Still, fixing them is faster than typing it all in.
DM, a lunch or something in August sounds good.
In putting together my collection of stories, I realized 2 predate having a computer file. So I flatbed-scanned one story from a book with sufficiently flexible spine, and I took photos of the pages of another book with a stiff spine while LCF pried it open. The result of both was a series of jpgs, one per page. I cleaned and straightened them in photoshop (maybe optional step), then uploaded the jpgs to google drive. There the magic happens. I select one of jpgs, right-click, and from the dropdown there's an OPEN WITH submenu. From that I choose Google Docs. After a few seconds of grinding, the jpg opens. But because I used Google Docs, beneath the jpg is a translation of the text in the jpg as actual text. I can copy and paste that into a Word doc.
As for voice to text, I've heard that for prose, Dragon isn't the best. Then again, I read that maybe 3 years ago, and I don't remember where. And this area is growing so fast. I tried using Microsoft's version 3 years ago, whatever it's called, and it kept bailing on me after a few words. Then I tried Google's version in Google docs, and it's nice--though it cuts out after a few paragaphs. My big problem at present is my handwriting. I'll jot paragaphs of revsisions in the margin of a story and decide it'd be faster to read it in than type it. But in voicing it, I'll hesitate a lot, because I can't read my own handwriting.
Fiction poses its own special problems for voice to text. Lots of long or unfamiliar or made-up words. Or strrange names like Kabita. So I'll just say K, but it still translates it differently each time--as K, or Kay, or Cay, or Kate, or Gay. Still, fixing them is faster than typing it all in.