Site Manager Developer Manual / Version 2010
Table Of Contents
You can activate the
Spellchecker
using the
<Spellchecker>
element in the
editor.xml
file.
Child elements:<MainDictionary>,
<CustomDictionary>
Parent elements:
<Editor>
<Editor>
[...]
<SpellChecker enabled="false" />
<SpellChecker enabled="true" os="Windows">
<MainDictionary class=
"com.coremedia.spellchecker.Bridge2JavaWordDictionary"/>
<CustomDictionary class=
"hox.corem.editor.spellchecker.Dictionary"/>
</SpellChecker>
[...]
</Editor>
Example 3.6. Example of a Spellchecker element
Caution
If you have activated the CoreMedia Spellchecker on your computer, and you want to use Word afterwards, you have to start Word with the "/w" option. Otherwise, all macros contained in a Word document that you want to edit later, would be executed without any warning.
This is because the CoreMedia Spellchecker starts a Word instance from an automation client for spell checking. This disables the macro security settings of Word. To circumvent this security problem, you have to start word with the "/w" option (see http://support.microsoft.com/kb/210565 for details).
| Attribute | Description |
|---|---|
enabled | This attribute determines whether the spellchecker should be used ("true") or should be disabled ("false"). By default, "false" is used. |
os | Restricts the configured spellchecker to a given operating system. The value is
compared to Java's system property os.name. Common value is for example
Windows. The configuration with the best (that is, longest) match wins. So
for example if you have a spellchecker configured with
os="Windows"
and
another with
os="Windows 7"
and you are running on Windows 7 the second
one will be taken. Default is to match all operating systems. So the example above
says: Disable the spellchecker on all operating systems but on Windows.
|
Table 3.10. Attribute of the element SpellChecker