My current Mac workflow: I copy the source from my email, use a vim script that removes HTML, leaving the text I wish to have read.Converting reformatted text from emails that I wish to have read to me at a later time.I use it in three specific ways, though a combination of the below defines 90% of my use-cases. I've long taken advantage of Mac's Text-to-Speech integration. I perform this only with Open Source tools, too, except for the "say" command. On my Mac, I can provide an input, and get an MP3 TTS file with no user intervention in-between, for my #1 scenario, below. I also wish to emphasize that "copy and paste into a third party TTS application" is unsatisfactory. For example in this 2012 SuperUser post, the questioner has the same issue, with no satisfactory answer provided. One of my use cases is for Narrator to only read selected text, as I outline below. Granted, my use-case isn't related to being visually-impaired. I've been through the Microsoft Narrator documentation, which I've found unhelpful. This post focuses on Text-to-Speech OS integration. Switching OS's, however, has two seemingly insurmountable areas which concern me. However, Apple's recent disappointing and lackluster focus on MacOS and their hardware, and a Lenovo X1 Yoga, 2nd Generation, has caught my attention. Apple's tight integration of POSIX-compliant file paths and a command line interface, and their historically strong hardware and manufacturing standards have had me on the Mac platform for years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |