Table of Contents
Advertisement
EWB100 Usage and Deployment Guide
Rev 1.13
Changing the meaning of a default clip is the same as redefining a device wide
clip and uses the same technique as describe above.
Directory Entries are the names of users or channels that are defined in the
directory. Typically such entries would be defined in the Flash or Ram tables,
although a user might use clips in the default dictionary (there are some clips in
the default dictionary for exactly this purpose). The directory is empty by default.
Entries to the directory are global across all profiles.
19.5 Multilanguage support
19.5.1 Basic Model
The EWB100 audio processing model has been designed from the beginning to
support multiple languages concurrently on the same device. This section
outlines how multiple languages could be supported now and what changes
could be added if the need arises.
As described above, every single audio clip defined in the default directory can
be replaced by another clip in another language. All that would be required would
be to define a set of click tables that contain audio clips with the same name as
those in the default table. These would be placed in Flash and would completely
replace the clips in the default tables. Alternatively one could selectively replace
only those clips that were actually used (since currently much of the default
dictionary is not used).
Replacing the default dictionary would allow the creation of a new and single
language version of the EWB100 device. All of the English clips would be
replaced by French or German or Spanish clips.
For the profile defined clips, the previously defined model works fine. One would
define new language clips and give them unique names. These names would be
assigned to profiles via configuration commands. The corresponding clip tables
would be stored in Flash (or RAM). When a profile was access that contained
one of these new clips, the system would do a lookup and build the correct clip-id
and use it going forward. One could have a French profile and a Spanish profile.
Each profile would use a unique set of clip names. The Flash clip table would
contain both sets of clips. Again all this is currently supported.
If one wanted to achieve multiple language support by combining the two
languages on phrase by phrase basis, one could also achieve this by creating
the dual language clips, assigning them unique names, and downloading a clip
table containing them. All this works using the current profile/audio clip model.
Directory entries would be global and so multiple language support would be less
robust. One could either go with global clips (people's names are generally
language independent) or go with a model in which the different forms of the
names are in a single clip (this would work for department names). Again, all this
works in the current implementation.
Page 96
Advertisement
Table of Contents
