Flanc,

I was not after language switching, but are you suggesting we change from 
text dictation, to a tiddlywiki command, using the same mechaisium?

Tones

On Wednesday, 11 August 2021 at 08:53:42 UTC+10 [email protected] wrote:

> @Tones, way ahead of you :) Already added command functionality for 
> language switching in new release. Updating Github Pages so drag and drop 
> is on correct version right now!
>
> On Tuesday, August 10, 2021 at 6:49:32 PM UTC-4 TW Tones wrote:
>
>> Flanc
>>
>> I think a design configuration is how do we trigger a more involved 
>> "command" on tiddlywiki. Perhaps we should leverage the existing keyboard 
>> shortcuts, such that either one can speak eg alt-space then the user can 
>> assign whatever they wish in response to that, ie trigger a set of actions. 
>> Of course in time "close tiddler" etc would be nice, but I think the key is 
>> the escape process, so lets say one can happily dictate any thing, except 
>> "OK TiddlyWiki" in which case rather than dictate into the current text 
>> field a dialogue opens in which the same dictation can search for any 
>> tiddlywiki designed terms, eg ok tiddlywiki, new tiddler (which you see on 
>> screen). 
>>
>> We have a way to detect what I call the focused tiddler eg;  
>> {{$:/HistoryList!!current-tiddler}}, for which such "ok tiddlywiki" can be 
>> designed to use as currentTiddler.
>>
>> The TiddlyWiki command plugin and others may be a short cut for us, to 
>> jump into, to move from dictation to commands. One could imagine where the 
>> user can assign what action or keyboard shortcut could be used as a result 
>> of "OK tiddlywiki". Only later we could see how to get the commands 
>> recognised in the middle of dictation, but I expect we still need this 
>> escape method.
>>
>> Regards
>> Tony
>> On Tuesday, 10 August 2021 at 22:57:36 UTC+10 [email protected] wrote:
>>
>>> Thanks everyone for the great advice! 
>>>
>>> My main takeaways for what I will start working on are commands: 
>>> punctuation, language switch, etc. 
>>>
>>> As this is on the side of the things I develop for the plug-in, I will 
>>> set to work immediately reading documentation and example code. 
>>>
>>> To get more technical,  I believe I can just attach a function to check 
>>> the last word of the transcription, and if it matches a set array of word/s 
>>> it will the execute a command. 
>>>
>>> BTC and I continue to talk on the Issues page of the repo, if any other 
>>> devs would like to chime in with other ideas/implementation, feel free to 
>>> chime in there. 
>>>
>>> Thanks again! 
>>>
>>> On Tue, Aug 10, 2021 at 6:32 AM R² <[email protected]> wrote:
>>>
>>>> Hi all and thanks Flank & BTC for this extremely promising plugin!
>>>>
>>>> Another few ideas and comments:
>>>>
>>>> (1) It would be nice to have a record button directly in the editor and 
>>>> not only have to rely on creating new transcript tiddlers.
>>>> (2) Automatic punctuation should be easy to switch on and off as per 
>>>> https://cloud.google.com/speech-to-text/docs/automatic-punctuation.
>>>> (3) There are quite a number of languages and accents available on the 
>>>> Web Speech API demo. It would be nice to be able to set the languageCode 
>>>> parameter manually (fully list at: 
>>>> https://cloud.google.com/speech-to-text/docs/languages). When this 
>>>> happens, could you make sure that custom record buttons can be added using 
>>>> only wikitext to allow multilingual users to have several record buttons 
>>>> based on their own needs?
>>>> (5) It could be worth mentioning in the readme that Google's Web Speech 
>>>> API demo at https://www.google.com/intl/en/chrome/demos/speech.html is 
>>>> a great way of checking for browser compatibility. I haven't found 
>>>> anything 
>>>> that works on my Linux system by the way. Any ideas as Firefox is 
>>>> unsupported and even Chromium strangely doesn't seem to be able to run the 
>>>> API on my system (V. 91.0.4472.114 on Linux Mint)? On my phone, Quinoid 
>>>> V1.0 doesn't work either :(
>>>> (6) Bouncing on TT's idea of using speech-driven commands while 
>>>> recording, this would make terrific sense not only for punctuation, but 
>>>> also to enunciate proper nouns for instance, or to switch languages on the 
>>>> fly within a given recording or prior to a recording ("switchtoItalian"…).
>>>> (7) I'm still running into problems regarding the short hearing span on 
>>>> the plugin's TW demo despite the version being seemingly v. 1.0.3.
>>>>
>>>> Thanks :)
>>>> R²
>>>>
>>>> -- 
>>>>
>>> You received this message because you are subscribed to the Google 
>>>> Groups "TiddlyWiki" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>>
>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywiki/367d80b8-aa58-471a-8c89-155f20c2cfa2n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywiki/367d80b8-aa58-471a-8c89-155f20c2cfa2n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b7cf8d32-7615-4458-9034-83850f27ce3bn%40googlegroups.com.

Reply via email to