Quick steps to create context starting from .BNF input file.

Please see the PC based Development Tools Users guide for a more elaborate explanation on LexTool

Open the Lexicon ToolKit.   (Start menu/Programs/L&H ASRAPI 1600 SDK/LexTool)
Import context.         (Menu Context/Import Context)
If this is the first time you do this you will be asked to create a user.
Select yes here. 
In the 'Create User' dialog you can enter a username of your choice.
You will be prompted to register that user, please do so.
In the next dialog window you can register several languages for that user.

Note: The concepts of user which have languages and contexts registered is only used in the
ASRAPI for the PC-platform. The embedded systems with the C/API do not use this.

When you have finished registering, you return to the 'Import Context' dialog window.
Here you need to enter your target language, your input bnf file and the name you want to give this context.
Note: On the PC-platform the L&H ASR engine has an internal database with contexts, users, languages, etc.
The name you give to this new context is used as identification in the ASRAPI database.

You should have an example bnf called adventur.bnf delivered with this sdk.
Enter the full path of this file in the 'Grammar File' edit box.
You can name the context 'Adventure'
Then click on the 'ok' button.
If no errors are found in the bnf file , you should get a confirmation that the import went successfull.
Note: If you have a PC with a soundblaster and a microphone you can test this context with the ASR Evaluator.

To use this context on the SET5 you need to export it to a file in the ASR1602 export format.
Click Menu/Context/Export Context.
Select the context and then click OK.
You will be asked to give two filenames.
The first one has an extension of .ctx which contains all the actual context information except 
for the result strings.
The second one has an extension of .wcl and this contains string information about the classes 
and words present in the context.


You can do recognition on an embedded system only using the .ctx and the word ids.
If you need the actual result strings on the embedded system you can use the .wcl.
To do this, first split the .wcl into a .wrd and a .cls.
With this you put the word information of .wcl into the .wrd file
With this you put the class information of .wcl into the .cls file
