Well it does, but there seems to be a problem:

I typed in John 671\John six seven one and it added the spoken form no problem(thru add words from list feature). Then I exported my custom words and DNS changed it to:John 671\\John six seven one. OK say it looks as though DNS has changed the formatting for added spoken words. Then I tried to add spoken forms using the \\ format and it just adds the word and not the spoken form.

So if you export you vocab and go to install in another profile etc with dragon having done the \\ for spoken then it won't add the spoken form.

Am i doing something wrong???

R

When importing a list which uses the new \\ separator, the first entry of the list must be "@Version=Plato".

I suppose that gives the option of if you want the spoken forms added or not. Any other reason you can think of??

I believe it is necessary to tell Dragon which format to expect.  With no initial flag, Dragon expects and uses the old \ separator.  With the initial flag included, Dragon expects the new one.

Ben & Rag,

Actually, DNS 11-11.5 automatically adds the "@Version=Plato" when you "Export custom word and phrase list". If you are creating your own personal custom word list, it isn't necessary to add that heading. The reason for this is that DNS 11-11.5 will accept word lists from previous versions of Dragon which do not use the \\ format. In fact, if you're creating a word list, it is much easier to use the old format with a single \ to separate Written forms from Spoken forms. In other words, it isn't necessary to use the DNS 11-11.5 format for creating custom word lists.

Otherwise, Ben is absolutely correct. That is, when adding a new custom word list, DNS 11-11.5 handles each list according to the format of the list itself as regards Written form\Spoken form or Written form\\Spoken form depending upon whether or not it contains the header @Version=Plato.

In short, it represents an awful lot of extra work that isn't necessary to use the DNS 11-11.5 format when creating your own personal custom word list.

Chuck Runquist
Technical Project Manager
VoiceTeach LLC
Home of VoicePower®: Simply powerful, powerfully simple

"A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila." -- Mitch Ratliffe

-------------------------

This is absolutely correct. The reason for this being a change in the underlying format of the vocabulary in the internal database. Also in previous versions, the vocabulary doesn't just consist of written forms and spoken forms, but each entry in the vocabulary optionally also comes with a third parameter which functions as some sort of word information.

This may come in handy for specific reasons, for instance when there are two different entries having the same written form but being different in terms of being distinguished by their word information (from a functional, for instance syntactical perspective).

The "old" format was:

Written form\spoken form\word information

The "new" format is:

Written form\word information\spoken form

Conventionally however and using the conventional built in vocabulary editor, you won't see the word information parts being involved, if there are any. But this is exactly why you would have to use two backslashes when adding custom words via lists containing a written form and a spoken form along with it, thus leaving out the word information part in the middle.

To understand this, please have a look at a custom vocabulary editor that I am currently building which also allows for displaying the word information part, if available, and please particularly look at the entries for the words "I" that I have selected in the screenshot, in order to demonstrate that they are actually different by referring to (a) the pronoun, and (b) the capital letter, as declared by their different word information parts.

Rüdiger

-------------------------

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!