Print ignores PaperSize

Stimulsoft Reports.WEB discussion
Post Reply
RossAFaneuf
Posts: 28
Joined: Thu Jul 28, 2011 9:16 am
Location: USA

Print ignores PaperSize

Post by RossAFaneuf »

We are a United States company who has customers who need to print on (for instance) A4 paper rather than the US default Letter paper (8.5 x 11 inches). They design reports which specify A4, and the following all work correctly, with the rendered report showing correctly sized pages:
- Rendering on any web browser
- Print to PDF

However, the Print operation itself ignores the A4 specification and renders the report using US 8.5 x 11" paper size. I have tried everything I can think of in the code to correct this behavior, including:
- Setting Stimulsoft.Report.StiOptions.Engine.DefaultPaperSize to the same value as the report
- Stimulsoft.Report.StiOptions.Print.CustomPaperSizes to match the report.

I assume that:
- these settings are actually for the Windows product
- the print engine is using the default printer settings for the web application back end (server), which typically does not have a printer configured at all.

One exception to the above: The Google/Chrome Cloud printing feature does seem to provide settings which cause print rendering to behave as desired, so that if a customer:
- Sets up Google cloud printing and
- Selects a printer which supports A4 paper

then the report renders correctly.

My question is:
Is there a way to provide settings or equivalent to the .Web print engine which causes it to recognize the paper specified in the report? We want to incorporate this in the server support code, because most of our customers are unwilling to use Chrome, or are not likely to configure cloud printing.
HighAley
Posts: 8430
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: Print ignores PaperSize

Post by HighAley »

Hello.
RossAFaneuf wrote:We are a United States company who has customers who need to print on (for instance) A4 paper rather than the US default Letter paper (8.5 x 11 inches). They design reports which specify A4, and the following all work correctly, with the rendered report showing correctly sized pages:
- Rendering on any web browser
- Print to PDF

However, the Print operation itself ignores the A4 specification and renders the report using US 8.5 x 11" paper size.
The report is not rendered again before printing. It is printed by browser.
RossAFaneuf wrote: I have tried everything I can think of in the code to correct this behavior, including:
- Setting Stimulsoft.Report.StiOptions.Engine.DefaultPaperSize to the same value as the report
- Stimulsoft.Report.StiOptions.Print.CustomPaperSizes to match the report.
These settings is for WinForms printing but not for Web.
RossAFaneuf wrote:I assume that:
- these settings are actually for the Windows product
- the print engine is using the default printer settings for the web application back end (server), which typically does not have a printer configured at all.
There is no any action on server when printing. The printing from web application could be from browser only.
RossAFaneuf wrote:One exception to the above: The Google/Chrome Cloud printing feature does seem to provide settings which cause print rendering to behave as desired, so that if a customer:
- Sets up Google cloud printing and
- Selects a printer which supports A4 paper

then the report renders correctly.

My question is:
Is there a way to provide settings or equivalent to the .Web print engine which causes it to recognize the paper specified in the report? We want to incorporate this in the server support code, because most of our customers are unwilling to use Chrome, or are not likely to configure cloud printing.
Summing up:
  • The server isn't used when clients print a report.
  • The report isn't rendered again before printing it is already rendered.
  • The browser send report to print using its print settings.
So user should set the printer settings in the browser printing dialog because it's impossible to change printer settings from web application.

Thank you.
Post Reply