Questions about AWTRenderer
Hi, all I have the some questions about FOP AWTRenderer: 1) What reasons to some Graphics2D rendering hints are not turned on by defaults? I mean the KEY_ANTIALIASING and KEY_FRACTIONALMETRICS. I have tried to turn them on and IMHO, FO looking is being pretty attractive and accurate. I believe what it could be the potential performance problem for the slow machines (or, maybe, some videocards), but we could make it possible to enabling/disabling by user (by the properties files or somehow else). But maybe there is a global Java2D properties somewhere? Then sorry, but I didnt find them... 2) I use the AWTRenderer in my own program for previewing the results before PDF generation or printing. Therefore, I want to have the precise snapshot of the future PDF. But it seems what AWT and AcroRead interpretes the font metrics differently, thus AWT preview doesnt looks like the PDF (or printed hardcopy). There is a differences between the linebreaks and pagebreaks locations, tables geometry etc. I have no ideas about how I can to make the precise preview, but maybe someone has? 3) What about wrapping AWTRenderer as the swing JComponent? It could be a more convenience to embedding it in applications. Thanks and sorry for my english, its ugly, I know. Best regards, Alex V. Alishevskikh [EMAIL PROTECTED] OpenMechanics http://www.openmechanics.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7608] New: - baseDir property not used when using custom fonts
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7608. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7608 baseDir property not used when using custom fonts Summary: baseDir property not used when using custom fonts Product: Fop Version: 0.20.3 Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The property baseDir is not used when custom fonts are specified. When a metrics file or a font file is loaded for embedding, and the specified filename is relative, Fop will always use the VM's working directory instead of baseDir. I have a limited fix that works for me, but I didn't research the FOP code well enough (and I don't want to while the code is being redesigned) to suggest this as a general patch. If someone wants to do this properly or just wants the fix for use, send email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: How to keep space between two region/block/ ... while rendering?
Anshuman wrote: Thanx for the useful tip. I am able to break the long table body into pages. But this led to another problem. I am using fo:static-content flow-name=xsl-region-after/ to put the footer in the page. But when the table breaks into more than one page, it overlaps the area of footer and breaks only at the very end of the page. How can I make the table break before the footer of the page ? You can define a fo:table-footer similar to the fo:table-header, so you don't really have to put table footer information into static content. As for overlapping, it's the same as for region-before: ensure the fo:region-body's margin-bottom is at least as large as the extent of the region-after. I thought this should be quite obvious meanwhile. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
