Or instead of removing the non-printable character replace it with an image scaled to fit a single character (like a lot of other applications do).
Jim Urban - [EMAIL PROTECTED] Park City Solutions Inc. Clinical Connectivity Suite Product Manager Suite 295 500 Park Blvd. Itasca, IL 60143 Voice: (630) 250-3045 x106 Fax: (630) 250-3046 CONFIDENTIALITY NOTICE This message and any included attachments are from Park City Solutions Inc. and are intended only for the entity to which it is addressed. The contained information is confidential and privileged material. If you are not the intended recipient, you are hereby notified that any use, dissemination, or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error please notify the sender of the delivery error by e-mail or call Park City Solutions Inc. corporate offices at (435) 654-0621 -----Original Message----- From: RamanaJV [mailto:[EMAIL PROTECTED]] Sent: Friday, July 12, 2002 10:03 AM To: [EMAIL PROTECTED] Subject: Non-printable characters HI FOP Developers, I found that whenever a non-printable character is found in the text of the FO document, FOP throws an error saying "Invalid XML character". Instead, I feel it's good to remove the non-printable character and proceed with the rendering. Ramana.JV. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
