You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reveiwed the tutoril I wrote last year, and about 80% of this https://talon.wiki/SettingUpTalonWindows10Dragon/ tutorial can be replaced by a link to the getting started page on talonvoice.com and an installation video. 80% of the information is redundant and the other 20% is incorrect or dated.
So I would replace that entire page with
a link to https://talonvoice.com/docs/index.html#getting-started
if they want to actually see a step-by-step installation of talon, I have this youtube video of installing Talon on Windows. We can refer them to it with a note to skip the wav2letter installation and install Dragon instead. https://youtu.be/wizshwYfuRo
This issue is pending me learning how to do a regular pull request.
The text was updated successfully, but these errors were encountered:
while I do agree that a step-by-step installation of talon and dragon is not needed I would suggest to explain how talon with dragon works. as I tried setting it up just days ago it would have helped to know that dragon keeps working the exact same way dragon works but talon is "hooked" in.
I reveiwed the tutoril I wrote last year, and about 80% of this https://talon.wiki/SettingUpTalonWindows10Dragon/ tutorial can be replaced by a link to the getting started page on talonvoice.com and an installation video. 80% of the information is redundant and the other 20% is incorrect or dated.
So I would replace that entire page with
a link to https://talonvoice.com/docs/index.html#getting-started
if they want to actually see a step-by-step installation of talon, I have this youtube video of installing Talon on Windows. We can refer them to it with a note to skip the wav2letter installation and install Dragon instead. https://youtu.be/wizshwYfuRo
This issue is pending me learning how to do a regular pull request.
The text was updated successfully, but these errors were encountered: