Never mind on this one. I was easily able to do:
com.lowagie.text.Image.getInstance(img, null);
and it all worked. Maybe that was not around in 1.3 when the other person
created it.
--
View this message in context:
http://www.nabble.com/ImgPostscript-tf4685260.html#a13417
Thank you Paulo. Is there another technique within iText to replace what it
used to do? I am not thinking my company here would feel comfortable having
me break apart jar files to pull in old class files. I might have to do
that though.
--
View this message in context:
http://www.nabble.co
day, October 24, 2007 7:29 PM
Subject: [iText-questions] ImgPostscript
>
> I just upgraded our product from using iText 1.3 to the latest 2.0.6 due
> to
> new requirements (XFA support). In doing so, some old bar code work
> somebody else did seems to not be working. Classes n
I just upgraded our product from using iText 1.3 to the latest 2.0.6 due to
new requirements (XFA support). In doing so, some old bar code work
somebody else did seems to not be working. Classes not found include
ImgPostscript and DocumentException.
com.lowagie.text.Image pdfImage =
The postscript part was contributed by Carsten Hammer.
- Original Message -
From: "Daniel Frey" <[EMAIL PROTECTED]>
To:
Sent: Friday, July 29, 2005 10:37 AM
Subject: [iText-questions] ImgPostscript defaults to 800x800
> Hello Paolo
>
> I am just looking why my
Hello
Paolo
I am just looking
why my postscript files are not placed correctly and met some lines which might
be the reason for it. In ImgPostscript, method processParameters seems to set
the height and width to 800, regardless of what was derived from the bounding
box:
125 processPara
