I'm really glad to hear that, Simon. Meanwhile we managed to resolve the problem appearing in Adobe Acrobat and Adobe Reader and the fix will be included in the next release of our product.

Ivan Hristov

Telerik Reporting

Hi Simon,

Sorry for being unclear. In R3 2020 SP1 the rendering of the SVG images in PDF is done using native PDF graphical primitives rather than rendering to a raster bitmap. The idea was to preserve the quality at all zoom levels in the PDF document. Our implementation is on experimental stage which means some of the SVG features are not supported. For example paths that use gradient fill will be rendered using solid color, obtained from the first of the gradient colors. Additionally some SVG files are not rendered correctly or at all by Adobe Acrobat/Adobe Acrobat Reader, while other applications like FoxIt PDF Reader or browsers like Chrome or Microsoft Edge have no problems with it. We're aware of these issues and we aim to fix them in a subsequent release of our product. If you have problems with the vector-based SVG rendering in PDF, you can always fall back to raster rendering by setting the key UseSvgVectorRendering to false in PDF Device Information Settings object.

All best,
Ivan Hristov
Telerik Reporting

Hi all,

I wanted to let you know that in R3 2020 SP1 we introduced basic support for vector rendering of SVG markup in PDF documents. Features like gradients, text-on-path and some advanced transformation over nested elements are not supported. In case the SVG you need to render in PDF contains some unsupported features that produce incorrect output, we advice to switch to raster rendering. This can be done through the PDF Device Information object and its key UseSvgVectorRendering. You can read more in the PDF Rendering Design Considerations article. 

All best,
Ivan Hristov
Telerik Reporting