My issue right now is with how Prince is interpreting text stroke widths.
My SVG’s are defining the stroke as just a non-unit specific numeric value, like ‘stroke-width="1"’. All SVG’s look correct in that the same stroke width of "1" seems to “scale” appropriately for both smaller and larger physical dimension documents. But in the PDF’s that are created, Prince appears to likely be interpreting this stroke width as 1 pixel or point other such non-scalable absolute value, such that the stroke on any larger dimension document becomes barely visible.
I'm confused how in all cases the SVG’s look correct in that text strokes scale up and down as appropriate with each SVG’s defined physical size, and yet they aren’t interpreted "correctly" by Prince. I don’t know how stroke is any different than other non-unit specific references within the SVG that do scale appropriately when converted to PDF.
If I'm simply not understanding something here, please forgive me.
Thanks!
My SVG’s are defining the stroke as just a non-unit specific numeric value, like ‘stroke-width="1"’. All SVG’s look correct in that the same stroke width of "1" seems to “scale” appropriately for both smaller and larger physical dimension documents. But in the PDF’s that are created, Prince appears to likely be interpreting this stroke width as 1 pixel or point other such non-scalable absolute value, such that the stroke on any larger dimension document becomes barely visible.
I'm confused how in all cases the SVG’s look correct in that text strokes scale up and down as appropriate with each SVG’s defined physical size, and yet they aren’t interpreted "correctly" by Prince. I don’t know how stroke is any different than other non-unit specific references within the SVG that do scale appropriately when converted to PDF.
If I'm simply not understanding something here, please forgive me.
Thanks!