🚀 go-pugleaf

Which command is ignoring the "pt" values?

How are you expecting a point to relate to a pixel? How far is the result off from your expectation? Just off a little or off by a 3:4 ratio, or something else?

- PostScript treats a point as 72/inch versus 72.27/inch.
- Acrobat uses 96 dpi
- The convertSVGToPDF has several attributes which might help resolve this for you See: userUnit and resolution.

If the SVG was generated in Illustrator, the Illustrator crop marks set the visible area. See the Knowledgebase article at:
 <http://support.adobe.com/devsup/devsup.nsf/docs/53357.htm>

If the above didn't help, explain more about the inconsistency you are seeing.

Bob,
The SVG is hand coded and what I am seeing is a PDF at the expected size but everything beyond the viewbox size is whited out. I know this because when I change the SVG width and height to be pixels and PDF it, the whole PDF edge is exactly where the blank part starts when I specify the same width and height as points. I hope that is clear.
So something is catching AGS off guard.

Strange thing is AGS is working as expected with other similar SVGs.

re: everything beyond viewbox is whited out
Isn't that the expected behaviour? Try opening the problem SVG in Internet Explorer and see how it displays there.

Bob,
It does display fine in IE.
I guess I wasn't clear in my description. The viewbox is set to pts so I expect a PDF at that point size. I am getting a PDF of that point size, however, after the rectangle of the same dimensions in pixels, the PDF is whited out. so if the viewbox is 100pts x 100pts I get a PDF at 100pts by 100pts but it is white after 100pixels x 100 pixels. Really wierd.

I'm not an SVG expert, but the above sounds like the opposite of what I'd expect. Typcially units are specified only for the height and width and then everything else is left unit-less as "user units". As in:

< ?xml version="1.0" standalone="no"?>
< !DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
< svg width="400pt" height="400pt" viewBox="0 0 400 400" xmlns="http://www.w3.org/2000/svg" version="1.1">

< rect x="1" y="1" width="398" height="398" fill="blue" stroke="red" stroke-width="2" />
< /svg>

From "Section 7.10 Units" of the SVG specification:

Note that use of px units or any other absolute unit identifiers can cause inconsistent visual results on different viewing environments since the size of "1px" may map to a different number of user units on different systems; thus, absolute units identifiers are only recommended for the width and the height on outermost 'svg' elements and situations where the content contains no transformations and it is desirable to specify values relative to the device pixel grid or to a particular real world unit size.

AGS allows you to use 72 or 96 for the userUnit attribute in convertSVGToPDF to mitigate some of these issues.

OK, how does one tell AGS to use one pixel dimension over the other? I think this would help and I am not seeing it in the docs.

<convertSVGToPDF pageSize="wd_unit, ht_unit" userUnit="num|num_unit" resolution="ndpi|dpc" />

userUnit is the user-space unit. This is used to interpret SVG length values specified
in pixels or user-space units. The default value is 1/96in.