This article is within the scope of WikiProject Technology, a collaborative effort to improve the coverage of technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
This article is within the scope of WikiProject Linguistics, a collaborative effort to improve the coverage of Linguistics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Yes that is correct it will not work with interviews. —Preceding unsigned comment added by 220.127.116.11 (talk) 23:21, 18 September 2010 (UTC)
Not exactly true. You can set up multiple users on a single installation of DNS, so that, e.g., each member of a family can have their own voice and language model and be recognized appropriately without confusion, as long as they always log in to their own user profile within DNS. And DNS has for a long time had the ability to recognize from recorded speech, with correction afterward. But it will probably do quite poorly on a single recording with multiple speakers. Proper ASR with any ASR software would probably require an intermediate step of speaker identification to split the recording into single-speaker segments, not only recognizing "There is a change of speaker here", but also "The new speaker is speaker A" (who was the speaker in, e.g., segments 1, 3, 6, and 9), so that all of each speaker's segments can benefit from correction on each other. --Thnidu (talk) 18:46, 7 August 2012 (UTC) (Senior Linguist, Dragon Systems, 1990-2001
I have rewritten the article and removed all instances of advertising or biased writing, and have included more citations. I have also tried to address what might have been considered to be original research. In addition, the "Issues" section was removed for two reasons: (i) it was out-of-date, and (ii) several sub-sections appeared to lack any references or evidence to support their allegations. If someone has a complaint about a product or a company's customer service, Wikipedia isn't the place for it. Spectral Diagram (talk) 00:36, 4 February 2010 (UTC)
Please do not add complaints to this article. Mephistophelian (talk) 21:01, 9 February 2010 (UTC)
Removed more advertising Kupiakos (talk) 20:37, 14 June 2013 (UTC)
The history of Dragon software, technology, products, and applications needs a major expansion. This software has a unique and valuable history. Its role in the development of speech recognition and applications should not be lost. Usually when companies write Wikipedia articles they sound like marketing materials. I hope the current owners might put that aside and see how an accurate and full history would be viewed as a major boost of reputation. Completing this task, if it can ever be fully complete, might require calling on the former stakeholders and employees, maybe even competitors. Johnswolter (talk) 20:02, 3 January 2012 (UTC)
I just added a reference to a journal article in which James Baker proposed a system called DRAGON, which I'm sure influenced the commercial product that he came out with 7 years later (though I haven't found a citation yet that explicitly points to that model as the precursor to the commercial system). Showeropera (talk) 17:26, 18 December 2012 (UTC)
The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.
The result of the move request was: no consensus. -- tariqabjotu 04:54, 12 August 2013 (UTC)
Oppose, the name of the product is "NaturallySpeaking" — we can't arbitrarily add a space there, that'd be like changing Toys "R" Us to Toys Are Us--Xiaphias (talk) 03:12, 25 July 2013 (UTC)
Oppose, the trademarked name is (CamelHumped) NaturallySpeaking. And, BTW, Toys-R-Us uses a backwards R. Checkingfax (talk) 03:21, 25 July 2013 (UTC)
Oppose. The product itself has an official typography which we can respect because it is not too strange, just camel-capped, which is allowed in many cases by Wikipedia:Manual of Style/Trademarks, and is in the remaining cases not changed to a space between the two parts, but is instead changed to all lower case after the first capital, such that Dragon NaturallySpeaking would become Dragon Naturallyspeaking. Binksternet (talk) 04:34, 25 July 2013 (UTC)
Support – In books, the more English-like version with the space has become more common. Per MOS:TM, then we should use that. Dicklyon (talk) 03:17, 30 July 2013 (UTC)
Oppose, Nuance uses NaturallySpeaking. Rjwilmsi 07:13, 30 July 2013 (UTC)
So you haven't actually looked at what the guideline MOS:TM suggests? Or you're suggesting we ignore it, for what reason? Dicklyon (talk) 14:04, 30 July 2013 (UTC)
Looked at it, it says CamelCase is a judgement call. In my judgement, from the sources I have seen relating to Dragon, the CamelCase form is in general use. Rjwilmsi 15:30, 30 July 2013 (UTC)
That's a more sensible argument than "Nuance uses NaturallySpeaking". But the spaced version is in even wider use, and is more English like, so why that judgement call? Dicklyon (talk) 15:37, 30 July 2013 (UTC)
Support per Dicklyon. If the proposed form is more common in sources now, there's no good reason to prefer the official name. --BDD (talk) 16:53, 30 July 2013 (UTC)
The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.