After spending spending all day yesterday at the location of the client who
is having the problem, we have determined that the problem relates to the
fact that the Adobe Acrobat plug-in for Firefox (and other browsers for
Windows) seems to determine that the pages in our document are not the
appropriate size. In the case of Windows, it determines a "shrink to fit
ratio" of 95%. This makes the labels too small. If we choose the "actual
size" option, then the labels print correctly. In IText, we are
specifying a page width of 792 points or 11" and a height of 612 points or
8.5". We have a top margin of 72 pts (1"); bottom margin of 94 pts (1.3:);
left and right margins of 58 pts (.8 "). What would trigger the Adobe
reader plug-in in Firefox, Chrome and IE to determine that the page is too
large and needs to be shrunk by 5%? We also did this on a couple of
different printers. Unfortunately, on the older Canon printer (used for
printing most labels) under Firefox there is not an option to specify the
actual page size option. So the problem can only be fixed by scaling up by
104%. This problem does not occur if we download the PDF file created and
use Adobe Reader directly. We can provide workarounds for the problem;
e.g., choose "actual size" if available or scale by 104% if not. However,
the client feels that these workarounds would be too confusing for their
average user to handle.
Is the problem that the Adobe plug-in deems that the 11X8.5 page is too
large for the printer or is the page size not actually determined by what
we specify to our IText Document object?. Any suggestions?
Cindy Jeness
On Fri, Jun 21, 2013 at 3:40 AM, iText Info <i...@1t3xt.info> wrote:
> Op 20/06/2013 18:30, Cynthia Jeness schreef:
> > No, we are not embedding. We defined the font as the Helvetica family
> > along with the font size and style in a separae parameter file and then
> > create the font as follows:
> >
> > Font font = new Font(FontFactory.getFont(
> > item.getFont().family,
> > fontSize,
> > item.getFont().style));
> >
> > Then we set it in the chunk that we are creating.
>
> Please take a look at figure 2.4 in this chapter:
> http://www.manning.com/lowagie2/samplechapter2.pdf
>
> Then read the text that comes with the figure.
> Does this describe the problem you're seeing?
> Or are you talking about something completely different?
> (Because you're not entirely clear in your question.)
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> iText-questions mailing list
> iText-questions@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/itext-questions
>
> iText(R) is a registered trademark of 1T3XT BVBA.
> Many questions posted to this list can (and will) be answered with a
> reference to the iText book: http://www.itextpdf.com/book/
> Please check the keywords list before you ask for examples:
> http://itextpdf.com/themes/keywords.php
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
