3 ms·
I’ve been experimenting recently with listening to my writing via a text-to-speech program as a part of the editing process. It’s great for noticing odd sentenc
by keiferski 3y ago
I’ve been experimenting recently with listening to my writing via a text-to-speech program as a part of the editing process. It’s great for noticing odd sentence patterns and overused words that are less obvious when reading.
This is different from merely reading it out loud by yourself, which doesn’t give you enough distance.
- earthboundkid 3y agoI’ve been doing this for many years. It’s a good strategy for catching typos like “the the” which your eye can just skip over.
- MathMonkeyMan 3y agoI'm going to try this. Any preferences for a low-fuss reader?
- keiferski 3y agoI just use the one built into Mac OSX actually. But Hearling.com is also a quick way to download audio files.
- voussoir 3y agoOn Windows, I use Balabolka to do this. There's also a Python package on pypi called pyttsx3, which I used to write a very simple command line program to say whatever is on my clipboard. http://www.cross-plus-a.com/balabolka.htm http://www.cross-plus-a.com/balabolka.htm https://pypi.org/project/pyttsx3/ https://pypi.org/project/pyttsx3/
- JuanPosadas 3y agoAsking ChatGPT/claude2 about a sentence/paragraph, with context like purpose of document (including non-fiction topic or fictional genre) has worked out really well for me. What I'd really like to do is have a standard "spell/grammar/plothole/tone/etc." critique prompt and have google docs start me from the top and roll down the entire document so we work on one sentence/paragraph at a time and see if I agree with anything pointed out or suggested. Right now there's a lot of copying/pasting, contextless critiquing, but at least claude will be able to read my full document for full context.