Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
SVG can just be imported into illustrator etc. converted to print ready PDF and sent to print.
Also much easier to convert the RGB colour space to CMYK on an SVG (as your CSS art would have to be screenshotted and then converted).
I mean I suppose I am splitting hairs as most print is digital nowadays, not litho, so the colour spaces are less important and, as you said, we can blow the CSS image up to a decent size and screen shot it so we can get the 300dpi we are after for most modern print jobs.
The only other thing with SVG is if you want spot UV etc. separating the layer off is probably easier (depending on how you build the CSS version of course).
But again, that's not SVG anymore, and it's only practical for large images. I could claim that screenshooting the CSS image is easier and faster than importing an SVG to Illustrator (but with a lot less features). CSS also supports CMYK (not all browsers though).
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
If we are screenshotting, we can just screenshot the SVG so I would call this one a draw if you just want an image 😋🤣
I don't think browser compatibility is a problem once we get into CMYK territory as I am saying to use a graphics package! So browser compatibility issues are not an issue here (in fact +1 for CSS art as it doesn't require any expensive software!)!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
SVG can just be imported into illustrator etc. converted to print ready PDF and sent to print.
Also much easier to convert the RGB colour space to CMYK on an SVG (as your CSS art would have to be screenshotted and then converted).
I mean I suppose I am splitting hairs as most print is digital nowadays, not litho, so the colour spaces are less important and, as you said, we can blow the CSS image up to a decent size and screen shot it so we can get the 300dpi we are after for most modern print jobs.
The only other thing with SVG is if you want spot UV etc. separating the layer off is probably easier (depending on how you build the CSS version of course).
But again, that's not SVG anymore, and it's only practical for large images. I could claim that screenshooting the CSS image is easier and faster than importing an SVG to Illustrator (but with a lot less features). CSS also supports CMYK (not all browsers though).
If we are screenshotting, we can just screenshot the SVG so I would call this one a draw if you just want an image 😋🤣
I don't think browser compatibility is a problem once we get into CMYK territory as I am saying to use a graphics package! So browser compatibility issues are not an issue here (in fact +1 for CSS art as it doesn't require any expensive software!)!