Svg.Skia produces more-complex-than-necessary SKPaths which result in rasterisation if rendered back out via e.g. Skia's PDF backend about svg.skia HOT 5 CLOSED

The version of skia pdf renderer that current SkiaSharp uses isn't best, it usually produces large pdf files and we use bit outdated skia, I would guess it got improved a lot. If you can repro that in latest skia I guess it would be nice to report upstream.

from svg.skia.

Fix confirmed with

<PackageReference Include="Svg.Skia" Version="1.0.0.10"/>

Loading SVG
Generated PDF to ./generated.pdf
Size of generated.pdf: 4046 bytes
Number of /Image instances in generated.pdf: 0
Number of /PatternType instances in generated.pdf: 0
Size of gold.pdf: 4046 bytes
Number of /Image instances in gold.pdf: 0
Number of /PatternType instances in gold.pdf: 0

Cheers!

from svg.skia.

Will release version 1.0.0.10 soon on NuGet so you can test.

from svg.skia.

Many thanks, appreciate it

Out of interest @wieslawsoltes - do you think there's an argument this is also a bug in Skia's PDF backend? Like, I still don't see why the shaders you were using should have caused a fallback to rasterisation at all: there's nothing in the docs here to suggest so: https://skia.org/docs/user/sample/pdf/ (unless "non-gradient SkShader" covers just basic color shader.. I don't see why it should though, gradients are more complicated than colour shaders)

Tempting to open a bug upstream too

from svg.skia.

@lol768 v1.0.0.10 is on NuGet

from svg.skia.