Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

When I print out PDFs from websites, their size is reduced and this didn't happen when I had MS Explorer.

  • 2 replies
  • 3 have this problem
  • 1 view
  • Last reply by socwrk3

socwrk3
socwrk3
more options

If I go into the website of an academic journal and access a PDF of an article and then print it, it comes out in much reduced size in the top lefthand corner of the document.

If I go into the website of an academic journal and access a PDF of an article and then print it, it comes out in much reduced size in the top lefthand corner of the document.

All Replies (2)

the-edmeister
the-edmeister
  • Moderator
more options

Check your Page Setup settings. https://support.mozilla.org/en-US/kb/how-print-websites#w_changing-the-page-setup Specifically the Scale and the Margins settings.

12.7 mm = metric paper sizes and .5 = inch- US paper sizes settings is default for the Margins

socwrk3
socwrk3 Question owner
more options

The answer refers to printing a web page. My question concerned a reduction in size when printing pdfs from websites. If I print a web page it works OK size-wise. If I print a pdf it doesn't. (Previously with Explorer pdfs from the same journals' web pages printed fine.) I could print the pdfs using the print function that prints out web pages in Firefox but that would introduce an extra stage into printing out articles and the quality isn't as good as printing directly from the pdf. As nothing has changed with the Adobe pdf software and the only change has been in my browser, I'm assuming the problem is somewhere in Firefox.