Kofax Communication Server 10.0.0 User Manual
Page 86
Client Applications
Administrator‘s Manual Version 10.0.0
©Kofax
86/187
7.3.4
Restrictions to Use of Cover Sheet Variables in RTF Covers
The variables in RTF cover sheets must not be interrupted by RTF command sequences. This
could happen if the style changes within the variable as in the following example which is
partially bold:
―$name$‖ would not be a valid variable and therefore not resolved because in the RTF stream
it would come out like ―$n\b ame$‖.
Cover sheet variables may be given in any style or font, which is then applied to the
replacement string, but the variable, has to be uniform.
7.3.5
Page Format
It is only possible to use Rich Text documents in portrait format in your coversheet. There is
no support for landscape format.
If you want to use a Rich Text document in portrait format your document should have the
width of A4 format (that is 210 mm). If the width of your document is smaller than 210 mm it is
automatically widened to 210 mm when it is attached to your coversheet. On the other hand
your document does not have to have the height of A4 format (= 297 mm). If the height of the
Rich Text document is smaller it is attached to your coversheet with no changes to its height.
Don‘t use Rich Text documents which are wider than 210 mm. Loss of text or word- line- or
page breaks in the preview/fax which differ from your original RTF document will occur.
7.3.6
Trace Options
In case of RTF conversion problems please create the following registry key:
HKLM\Software\TOPCALL\TCOSS\rtfTraceLevel REG_DWORD 0
rtfTraceLevel is bit wise interpreted. The meaning of the single bits is defined as below:
0x01 ... errors (if any bit is set errors are traced)
0x02 ... warnings
0x04 ... info on memory allocated - freed
0x08 ... info on (gdi/window) objects used
0x10 ... info on thread execution
0x20 ... common info
0x80 ... TraceInfo - output of info concerning trace classes (not implemented yet)