I ran under 1.4.1_01 and updated to _02. There was no change... I think there must be some difference in drivers of the two printers, that seem to define additionally to the XSL:FO definition of the margins their own (default) margins. I see that this is not 100% FOP question but perhaps someone in here has some experiences with printing to different printers and can share Knowledge!?
Greetings Normen -----Urspr�ngliche Nachricht----- Von: Clay Leeds [mailto:[EMAIL PROTECTED] Gesendet: Montag, 10. M�rz 2003 22:40 An: [EMAIL PROTECTED] Betreff: Re: left margin different on two printouts... Normen Ruhrus wrote: > Hi there, i wrote a servlet that supports pdf streaming to a browser > (works fine) and printing (server side) using the awtrenderer. Problem > here is, on one printer it looks just fine while on the other one some > parts are cut off... Well it looks like that its not the font metric > problem. One of the two printers (HP V40) makes a bigger left margin > than a Samsung laserprinter, while they are using the 100% same source. > Is this a printer driver problem? Is there an explanation / workaround > ??? Hope someone can help me out... Thanks in advance Normen > Ruhrus (Much of this message mirrors the previous answer I gave, however there is a bit more information below.) In our testing at my company, we've found that the version of Java being used may affect the output. In particular, there was a bug in pre-1.4.x Sun java that had FontMetrics issues. IBM 1.30 java appears to be unaffected by this bug. As a result, we've indicated to our clients that our FOP implementation requires Sun Java 1.4.1+ or IBM Java 1.30+. If you're having problems, see if you can install one of these JAVA upgrades (you shouldn't need to change the server to default to this new version to test. Just open a new terminal window, and set $JAVA_HOME to that new version of JAVA), and then do more testing. If you find it works, that may be the culprit. However, you'll want to test any other applications currently running on your server to make certain nothing "breaks" with the updated JRE before you implement the change. HTH! -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
