 Speech ComputingWhere Speech Meets Computing |
|
User loginRegistering and logging in removes this ad.
--- Registering and logging in removes this ad. |
Problem with capitalization of a word after period close-smart-quote
Submitted by Akhavan on Thu, 10/16/2008 - 10:05.
Hi, In DNS Pro 9.5 when I had a period followed by close-smart-quote then the next word would start with capitalization for example “It's okay.” However,….. Now, with DNS Pro 10 it doesn't happen. For example, “It's okay.” however…. It doesn't capitalize the word however Is there a way to fix it? Sepehr  |
NavigationPopular content
Who's onlineThere are currently 0 users and 6 guests online.
|
NOTICE OF DISCLAIMER: All readers, visitors and/or users of this site is/are hereby given notice that any and all either express or implied views, opinions, suggestions, advice, product promotions, and/or any apparent statements of truths or facts that have been, presently are or in the future may be placed on this site are to be understood to be solely those of the party posting same. In no regard or event are any or all express or implied views, opinions, suggestions, advice, product promotions, and/or any apparent statements of truths or facts posted on this site in any way whatsoever to be either directly or indirectly understood, interpreted, construed or relied upon by any readers, visitors and/or users of this site as being expressed or purveyed by or representative of the host of this site, nor shall same be directly or indirectly understood, interpreted, construed or relied upon by any readers as an endorsement of same by the host of this site. Any and all such express or implied views, opinions, suggestions, advice, product promotions, and any/or apparent statements of truths or facts posted on this site should be thoroughly investigated independently by any and all readers, visitors and/or users of this site prior to relying or acting upon same in any way or at any time.
© 2005-2010 Speech Computing
Best Viewed at 1024x768 and higher resolutions
You could try changing its
You could try changing its properties. Refer to the following topic for an overview:
http://www.speechcomputing.com/node/1646
Bruce
Well, it doesn't work for me
Well, it doesn't work for me either. I notice that “open-quote” and its ilk have a notation about having special properties that can't be changed, and I suspect its those “special properties” that we want -- but apparently they are part of Nuance's proprietary formatting rules. There is no obvious way to copy and modify one of these words so as to covertly copy the special formatting.
Maybe we can get Chuck Runquist to weigh in on this issue.
Bruce
Akhavan wrote: Hi, In DNS
Hi,
In DNS Pro 9.5 when I had a period followed by close-smart-quote then the next word would start with capitalization for example “It's okay.” However,…..
Now, with DNS Pro 10 it doesn't happen. For example, “It's okay.” however…. It doesn't capitalize the word however
Is there a way to fix it?
Sepehr
Sepehr,
In DNS 9.5 you were allowed to modify the properties and/or create curly quotes/smart quotes which would follow the normal capitalization rules after terminal punctuation. You could do this by either modifying current quotation marks and adding an alternate written form, or adding your own using either the written form or the alternate written form. You cannot do this in DNS 10 because of the formatting changes. If you remember, there were multiple problems with capitalization after terminal punctuation in DNS 9.5 by allowing this process.
However, in DNS 10 this has changed. If you go to the Vocabulary Editor and select the properties on any of the quotation mark entries, you will see that there is a message at the top of the properties screen that says “This word has special properties that cannot be changed.” The reason for this is that DNS 10 has corrected a problem with the capitalization after terminal punctuation that occurred in DNS 9.5. For special characters like quotation marks and a couple of others, the properties cannot be changed because the new ITN rules create special properties for these "words" so that they properly detect terminal punctuation.
Also, in DNS 10, you can't simply add custom quotation mark by entering the standard (") in the written form because DNS 10 will not allow you to enter duplicate words, symbols, punctuation, etc.
Nevertheless, there is a way to do this, but it involves creating 2 copies of the ending quote (curly quote). You should have one copy for normal quotations that aren't preceded by terminal punctuation and one copy for those that are. For example, I have created the following vocabulary entries:
1. Alt+0147 to enter the starting quote (smart quote/curly quote) for the written form, "smart-quote" for the spoken form, making sure that the properties are properly set for spacing (i.e., 1 space before (and) 0 spaces after)
2. Alt+0148 to enter the ending quote (smart quote/curly quote) for the written form, "close-smart-quote" for the spoken form, making sure that the properties are properly set for spacing (i.e., 0 spaces before (and) 1 space after).
The above two entries will take care of the normal use (i.e., no terminal punctuation before the ending curly quote).
3. Alt+0148 to enter the ending quote (smart quote/curly quote) for the written form "close-curly-quote" for the spoken form, setting the properties for spacing to 0 spaces (and) 1 space after, and "Format the next word" capitalized.
The above entry will take care of the problem with using the curly quotes after terminal punctuation.
I strongly advise you to use the spoken forms as I have used above. Please note the hyphens and the differences between smart-quote, close-smart-quote, and close-curly-quote. Is so that you have a way of distinguishing between the two types of ending curly quotes. These formats for the spoken form work perfectly for me and they are easy to remember. The reason they're easy to remember is that the actual term for this type of quotation mark is "smart-quote", not "curly-quote." However, using close-curly-quote after periods, question marks, exclamation marks, etc. will always capitalize the following word, which is what you are asking for. Remember the acronym KISS (Keep It Simple Stupid). Using this approach does just that, along with the fact that it is easy to use and remember these.
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS with Lernout & Hauspie (L&H)
"Life's Rule #1: Once you pull the pin, Mr. Grenade is no longer your friend." (Variant of Murphy's Law - Edward A. Murphy, Jr)
It seems one problem solved
It seems one problem solved creates a new one.
It gets time Nuance gives clear information about all these formatting and ITN issues in a good, concise and complete document. It is too bad that we get this information only through a "Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS with Lernout & Hauspie (L&H)".
Quintijn
Hi Chuck, I have done
Hi Chuck,
I have done exactly what you have described above. In fact, I learned it from one of your earlier posts. Thanks BTW
Right now I have "Format the next word 'with normal capitalization'" However, if I change it as you suggest above to "Format the next word 'Capitalized'" then if the quotation is not after a period it will capitalize the next word in the middle of the sentence which will be wrong again.
Sepehr
Akhavan wrote: Hi Chuck, I
Hi Chuck,
I have done exactly what you have described above. In fact, I learned it from one of your earlier posts. Thanks BTW
Right now I have "Format the next word 'with normal capitalization'" However, if I change it as you suggest above to "Format the next word 'Capitalized'" then if the quotation is not after a period it will capitalize the next word in the middle of the sentence which will be wrong again.
Sepehr
Sepehr,
Apparently you didn't read my post clearly. What I said was you create to distinctly different versions of the close-curly-quote commands. One you set up for normal use, and one you set up for use after terminal punctuation.
Read my post again. You set your two primary curly quote entries as "smart-quote" and "close-smart-quote". The first one doesn't need change because it doesn't involve terminal punctuation. The second one you keep with the normal settings (normal capitalization) for use with out terminal punctuation. Then you create a third curly quote entry, but you set the spoken form as close-curly-quote and you set the properties to capitalized the next word. Then, when dictating a curly quote after the terminal punctuation mark, you say "close-curly-quote". When you're dictating normally you use the "close-smart-quote". Remember the two are different and you use each based on whether or not you are dictating such after terminal punctuation or in the middle of a sentence.
Let me reiterate. I said to create three different entries: (1) create an open curly quote entry for use across the board in all cases, (2) create a close-curly-quote entry for use in normal circumstances when dictating in the middle of a sentence and not following terminal punctuation, and (3) create a close-curly-quote entry for use after terminal punctuation. 2 and 3 have to have different spoken forms. I also said that the normal spoken forms (normal capitalization) should use the same basic terminology, but the third spoken form should use a different spoken form term.
Again, smart-quote, close-smart-quote, and close-curly-quote.
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS
I know that you believe you understand what you think I said, but, I am not sure you realize that what you heard is not what I meant.
Hi Chuck,You were right I
Hi Chuck,
You were right I wasn't paying attention. I just did it and it works dandy. Thanks
Sepehr