@flanc, I tested it once more- after importing the danish language plugin 
and it did write some sentences correct...and some rather amusing. It will 
be very useable though. In fact it is much better than I had hoped for, 
Danish being used by so few people. So nice, I know I will use this a lot. 

Thank you so much for all the work you and BurningTreeC are doing on this.

Birthe


On Wednesday, August 11, 2021 at 3:03:56 PM UTC+2 [email protected] wrote:

> @Strikke…, yes. Any language shown on the demo is theoretically be 
> supported by the plug-in. I’m not sure if there is a Danish translation of 
> TW. With my new idea to just use the TW language, there may be some 
> limitation. 
>
> On Wed, Aug 11, 2021 at 9:01 AM [email protected] <[email protected]> 
> wrote:
>
>>
>> Hi flanc,
>> I followed the link to Web Speech API 
>> <http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html> 
>> Demonstration. 
>> Danish can be used, will it also be possible to use it using your plugin 
>> with Danish?
>>
>> Birthe
>>
>> On Wednesday, August 11, 2021 at 2:11:12 PM UTC+2 [email protected] 
>> wrote:
>>
>>> Love the feedback! 
>>>
>>> Something to do with the language names. Each of those language names 
>>> were decided rather carefully, since, for example, catalan was understood 
>>> in a different word every time, but the word "catalonian" was transcribed 
>>> with perfect accuracy. One possible solution would be to test for a variety 
>>> of different words that sound like the keyword, similar to what BTC did 
>>> with the new "Ok Wiki" functionality, and that would require you awesome 
>>> folks to test the words, and report back what they are transcribed as.
>>>
>>> In addition to this, I forgot to add, there are multiple variants of 
>>> several languages, such as english US, UK, Australian, South African; 
>>> spanish Spain, etc. etc. I plan to add all of this functionality sometime 
>>> soon, as well.
>>>
>>> For all of the languages the API supports that my little wrapper program 
>>> could easily be changed to modify, they are listed in this StackOverflow 
>>> post: https://stackoverflow.com/a/23733589/14719982. Feel free to speak 
>>> the translated language names into the plugin, and see what they are 
>>> transcribed as.
>>>
>>> (Since the default lang I have set is English-US, the language names 
>>> must sadly be translated into English to be understood, such as Espanol to 
>>> Spanish. This also accounts for maybe "improper" languages names, as 
>>> pointed out.)
>>> On Wednesday, August 11, 2021 at 4:41:54 AM UTC-4 BurningTreeC wrote:
>>>
>>>> Hello all, I've now changed the *Command *command to *Ok Wiki*
>>>>
>>>> I've made it also detect Okay Vicky, Ok WC, and more keywords ... If 
>>>> those of you who are testing this would report any other keywords we 
>>>> should 
>>>> add, that would be a great help
>>>>
>>>> What should work right now is *Ok Wiki change language to <<language>> 
>>>> *and *Ok Wiki stop talking*
>>>>
>>>>
>>>>
>>>> TiddlyTweeter schrieb am Mittwoch, 11. August 2021 um 10:28:45 UTC+2:
>>>>
>>>>> Ciao Flanc... & BTC
>>>>>
>>>>> *SIDE NOTES ON API BEHAVIOR*
>>>>>
>>>>> This does not effect anything YOU two are doing. Merely observations 
>>>>> on the "behaviours" of the recognitions. 
>>>>> But I do think it is useful to understand the end-product the API 
>>>>> issues forth.
>>>>>
>>>>> *1 -* There are occasional QUIRKY things that happen that have no 
>>>>> clear rationale. For instance if you dictate "cat dog mouse horse" you 
>>>>> get 
>>>>> back ... "cat dog Mouse horse". Maybe mice, or mouses, actually rule 
>>>>> the universe as "The Hitchhiker's Guide To The Galaxy" contended"? 
>>>>> <https://www.bbc.co.uk/programmes/profiles/1MmQjXrkwp98jNdc17j3tr3/mice>
>>>>>
>>>>> *2 -* Sometimes words that are not understood by the api are simply 
>>>>> DISCARDED. (For instance in Italian mode most dictated English words are 
>>>>> just ignored).
>>>>>
>>>>> *3 - * Sometimes words that are not understood by the api are 
>>>>> capitalized as Proper Names. There is some very clever thing going on 
>>>>> inside the recog. machine that decides when to do this.
>>>>>
>>>>> None of these minor points change anything other than the need to be 
>>>>> slightly aware the API does stuff and awareness of that is helpful I 
>>>>> think.
>>>>>
>>>>> I'll may add more comments about these behaviors after I used it more, 
>>>>> if there any other obvious ones. 
>>>>>
>>>>> Best wishes
>>>>> TT
>>>>>
>>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/3O0eT4K5mkI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/1059a0eb-2708-4946-b04f-84a6e320c4dcn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/1059a0eb-2708-4946-b04f-84a6e320c4dcn%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/af5ec459-8703-41f4-bb09-77f68353ed52n%40googlegroups.com.

Reply via email to