Save to SVG Bug

[arisse22]

We have discovered what we believe to be 2 bugs in Spire.PDF related to saving PDFs to SVG. It's also possible that it's a single bug that is manifesting itself in different ways.

Bug #1 (the main one): We can't give a simple reproduction. We have a long running Windows Service that does many things, but among these things it converts PDFs to SVG and occasionally the generated SVG files are incorrect. The attached zip contains a TestFiles\ActualBug folder with examples. The folder contains a good SVG file and a bad one. Both were generated from TestFiles\Original.pdf. The resulting SVG files differ by a few things, but the font tables seem key. This bug occurs for us almost daily, but is intermittent and we can't give a simple method to reproduce. Our code simply loads a PDF and saves as SVG so there's nothing interesting. The attached zip contains code that is identical to what our service is doing.

A few more things about Bug #1
- Once it starts happening, every PDF->SVG operation thereafter exhibits the problem and the fonts within the SVG are incorrect.
- It typically takes about a day or more of processing before the problem occurs.
- Restarting the service clears things up, for a while until it happens again.

Bug #2: This one is easy to reproduce, and the attached zip contains a Console app that exhibits the problem. The first time an SVG is created from PDF the SVG is ok. However, if the same PdfDocument is used to generate another SVG, the second SVG is incorrect and is completely missing a font table. See TestFiles\Bad.svg and TestFiles\Good.svg for example output or simply run the attached program. Note that saving to HTML is similar since internally PdfDocument seems to use SVG for creating HTML.


Since both bugs are related to the SVG font table we are hoping that addressing the 2nd one might somehow help with the first. To be clear, we are really interested in Bug#1, we just discovered Bug#2 while researching this issue.

We are using Spire.PDF 10.12.4 but have seen this for older versions as well.
We are running on Windows 11 and Windows Server 2022 and both exhibit the issue

[amy.zhao]

Hello Alan Risse,

Thank you for your feedback.

I have managed to reproduce Bug #2 based on the code and documentation you provided. I sincerely apologize for any inconvenience this has caused. The issue has been logged into our system with the reference number SPIREPDF-7301 and has been assigned the highest priority. We will address it as quickly as possible.

I suspect that Bug #1 may also be related to this issue. Once we have resolved SPIREPDF-7301, we will promptly provide you with a patched version for testing to see if it resolves both Bug #1 and Bug #2 simultaneously.

Thank you for your patience and understanding. If you have any further questions or need additional assistance, please do not hesitate to contact us.

Sincerely,
Amy
E-iceblue support team

[amy.zhao]

Hello,

Thank you for your patience.

I'm glad to inform you that SPIREPDF-7301 has been resolved. Welcome to download and test [Spire.PDF Pack(Hot Fix) Version:11.1.0].
Our website link: https://www.e-iceblue.com/Download/download-pdf-for-net-now.html
NuGet link: https://www.nuget.org/packages/Spire.PDF/11.1.0

If you have any questions, please let us know.

Sincerely,
Amy
E-iceblue support team

[arisse22]

Ever since upgrading to 11.0.x, I get the "Evaluation Warning : The document was created with Spire.PDF for .NET." when creating SVG. This does not occur on the first SVG that is generated, but after the first this occurs every time. I have tried 11.1.0 and 11.2.4 and both exhibit this behavior. I am wondering if my license file is valid after the bugfix/upgrade. Please advise.

Thanks,

A

[Nina.Tang]

Hello,

After reviewing your purchase information, we found that your company has acquired the Spire.PDF for .NET Developer Small Business. Please note that this subscription permits usage by 1 developer and 1 deployment location, each identified by a unique MAC address. Using our product on machines that exceed these limits will result in watermarks appearing.

The Developer Small Business license is not sufficient for your usage scenario. We recommend upgrading to the Developer OEM (unlimited MAC addresses) license type, which provides more flexibility and can be used across multiple locations.

If you need upgrade the license or have any further questions, please do not hesitate to contact us.

Sincerely,
Nina
E-iceblue support team