Are the AWTRenderer spacing fixes in a release version of FOP? If so, which version?
Thanks, 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: Ralph LaChance [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 3:11 PM To: [EMAIL PROTECTED] Subject: Re: TIFFRenderer At 10:11 AM 5/21/02, you wrote: >Ralph LaChance is working on it. Check the current CVS. Ralph's diff >should have improved some of this. But it seems like AWT still has its >pitfalls. > >Implementing a full bitmap renderer without the use of AWT would be a >major pile of work, I think. But you can always try to use GhostScript >to convert a PDF/PS to TIFF which should have about the same qualities >as the PDF. Which method are you using right now? Actually, I (biased!) think the present awt renderer is quite good; the character spacings problems within words that existed in previous versions is fixed, and text decorations seem to work correctly. As Jeremias pointed out, I am chasing a new problem - but that one doesn't really bear on awt itself, but shows up only when the awt renderer is used to print. (The problem appears if fop is run w/ -print option or if the print command is invoked on the -awt display dialog.) Offhand, I do not expect the printing problem to show up if the awt renderer were used as the basis for a tiff renderer. We believe the printing problem stems from a java bug around fonts - the character rasterizer seems to be ending up with text strings being improperly sized when it is drawing into a graphics context created by a PrinterJob. There are several related bugs in the bug parade on this matter. ' Best, -Ralph LaChance --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
