Kofax Communication Server 9.1.1 - Manual (Page 202)

Client Applications Administrato r‘s Manual Version 9.1.1
©Kofax, Inc. 202/204
Graphic objects inserted into RTF document in Word via Insert/Object will be sent;
however, the images may be distorted.
A better way to handle graphics is to make it in an overlay so that it is stored in TCI format.
Another way to do this without an overlay is to insert the graphic block as a bitmap file in
the cover or in a template.
Avoid writing directly at the right/left margin. If the paper of the receiving FAX machine is
not properly put into the machine, loss of text might be the result.
Be aware of memory usage. For example 120 FAX channels on TCOSS which support
RTF coversheets will take approximately 250 MB memory.
Overlays, header- and footer lines are not supported by TCRtf.
Any fonts not included in standard Windows must be manually installed on the KCS server,
TC/LINK server and any client PC that provides KCS FAX Preview.
As mentioned above – coversheet variables may not be interrupted by rtf command
sequences.
As mentioned in the last chapter, do not 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.
RTF files containing characters which are not included in 7 bit ASCII code must specify
ANSI
Codepage 1250, 1252 or 932 in the \ansicpg statement.
You have to create your RTF document according to the rules for page format as
previously described. If you disobey them, parts of your document may be lost when
attaching it to your coversheet and word- line- or page breaks may differ. This means
especially that you have to use a portrait Rich Text document. There is no support for
landscape.
Coversheets of delivery notification created by a Link may not include RichText.