Caps Dictation Commands Not Working Anymore

On my iPad I found a workaround. If you double tap the caps key on the keyboard, dictation will make all words capitalize. Likewise, if the caps key is that for capitalizing the letter of the first word you type the same will happen for the first word you dictate and so on.

I find the above doesn't hold true, however, when the keyboard automatically set the caps key. For example, after making a period and space for a new sentence.

Thanks for your suggestion, but I'm not sure I'd call it a "workaround", because it doesn't really work around the problem and make the dictation work as it is supposed to. Hitting the cap key and then going into dictation only gets the first word to capitalize. And, double-tapping the cap key to get all the words to be capital means that one has to stop dictation, double-tap the caps key, start dictation, speak, and then stop dictation to undo the double-tapped caps key. It's a lot of work for something that's supposed to work without fingertip intervention. Let's hope someone at Apple is listening....!!

True, but that's why I called it a workaround and not a fix. At least I'm able to capitalize an entire sentence if I need to. Almost useless to use for single capitalization, though. :(

I really hope they fix it soon.

I'm also finding on my iPhone 4s, I can't dictate 'period" as in "Have a great day period" because that's literally what it types. Seems okay on the iPad though

For periods, I find that if you pause about a half or second or more before stoping dictation will dramatically increase the chance that it'll type that period or the last word I said correctly.

I'm skeptical that reporting this issue through the iPad or iPhone feedback pages will help. Apple engineers are undoubtedly already aware of this issue if for no other reason than they use Siri themselves and are experiencing the same problem. Furthermore my guess is that this sudden non-functionality is by design - somebody at Apple decided for some reason that the "caps" commands (and others like "numeral" that have also been affected) should be disabled. This is admittedly speculation by why else would something that works fine one day just suddenly stop working the next?

My logic is also along the same lines. But, it still might be a good idea to report it to the link above, just in case.

I'm now having this issue with the current version of mountain lion. Did anyone find a fix to it? Thanks.

I'm having the same problem in Mountain Lion as well, in addition to the capitalization commands, certain dictation commands like "no space" (which is supposed to omit the space between dictated words) and "number two" or "numeral two" (both of which are supposed to type "2") aren't working anymore on my Mountain Lion computer or any of my iOS devices.

I am convinced this is not a bug but, rather, an intentional move by Apple. I suspect providing feedback to them via the usual mechanism is the only way to get this features set restored.

Why would they intentionally place something like this?

I hope it's not an intentional omission! It's pretty much been killing Siri's utility for me – turns out I capitalize a lot more words than I thought I did!

Plus in any guides I see about functions in dictation, it mentions all the features that do not work for me.

They better fix it soon! If it's been that way in Siri, then who know how long it will be!

There is a rumor that Apple licensed this technology from Dragon systems. Perhaps this is the result of a contract dispute that reared its ugly head sometime after Siri was initially released. Perhaps Dragon realized that, unless they took a stand on the issue, Apple's incorporation of voice-to-text on both platforms would kill Dragon's market.

I'm with Powsner on this one. Apple did license this technology from Nuance. As a long time Dragon user, I was thrilled to be able to use all the familiar commands like "open paren", "caps on", "caps off", "new line", "numeral two", "em dash" etc.

Now none of these "Nuance" commands are working. This cannot be an accident or glitch.

Like Apple casting out Google Maps for Apple Maps, I suspect we are seeing Nuance Dictation being cast out for Apple Dictation -- without any announcement or notice. Or Nuance is cutting Apple off due to falling sales of its desktop solutions -- right around the time Mountail Lion comes out.

Very sad. I am a heavy dictation user who was looking forward to native dictation in Mountain Lion. Without "caps on" and "caps off" however, it's useless.

I got a Nexus 7 to try Jelly Bean's offline mobile dictation. Initailly very promising, but guess what commands it doesn't support.... "new line" and "new paragraph". So it is completely useless unless you only want to dictate one continuous line of text.

I'm beginning to think Nuance is trying to copyright these commands, and is disallowing them from Apple and Android products.

Please post if you learn anything about this apparently puposeful deactivation of features, or knowi anything about the Android dictation limitations, as both mobile solutions are useless with these current limitations.