You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cairo is expecting to receive the canvas size in points, but it is actually receiving the size in pixels which results in an output image that is larger than expected. e.g. mapfile map size of 300 x 300 (pixels) -> cairo svg of 300 x 300 points which is 375 x 375 pixels at 90 dpi which the programs I tested with seem to assume (Inkscape, Chrome, Firefox).
The text was updated successfully, but these errors were encountered:
Does anyone work on this problem?
Looks like the PDF canvas size should be calculated from the map image size according to the DPI setting specified for the map.
From: Tamas Szekeres [mailto:notifications@github.com]
Sent: Monday, November 03, 2014 6:54 AM
To: mapserver/mapserver
Subject: Re: [mapserver] Cairo SVG and PDF output larger than PNG (#4487)
Does anyone work on this problem?
Looks like the PDF canvas size should be calculated from the map image size according to the DPI setting specified for the map.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4487#issuecomment-61473401.
This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.
Typically, issues fall in this state for one of the following reasons:
Hard, impossible or not enough information to reproduce
Missing test case
Lack of a champion with interest and/or funding to address the issue
Cairo is expecting to receive the canvas size in points, but it is actually receiving the size in pixels which results in an output image that is larger than expected. e.g. mapfile map size of 300 x 300 (pixels) -> cairo svg of 300 x 300 points which is 375 x 375 pixels at 90 dpi which the programs I tested with seem to assume (Inkscape, Chrome, Firefox).
The text was updated successfully, but these errors were encountered: