Thanks for providing the information. We have taken it into our account and will consider during the investigation. We will surely request for the information in case we need some from your end related to the ticket. We are sorry for the inconvenience.
Thank you for your response and for taking the information into account as part of your investigation.
I’m writing to kindly follow up on the status of the ticket, as this is a priority issue for us. We would appreciate it if you could look into it at the earliest possible opportunity. Please let me know if any further information is required from my side to assist with the resolution.
Looking forward to your prompt response.
Thanks for your patience. We have already been investigating the issue. To proceed effectively, we kindly request a few more details to help us reproduce the problem accurately, as we’re currently unable to replicate the issue on our side:
Does the issue occur when generating a completely new/empty PDF, or are you modifying an existing document that may already contain Arial?
Could you provide sample content used in OriginalInformation and NewInformation, especially the data that causes the rendering or overflow issue?
Which framework or SDK version are you using (e.g., .NET 6, .NET Core 3.1)?
Most importantly, please share a minimal, isolated code sample that includes:
- The relevant code to generate the PDF with HtmlFragment
- Sample data and inputs
- Any template or related files, if applicable
Thank you for your previous response.
To reiterate and provide clarity on the pending issue:
- PDF Source: We are modifying an existing PDF—not generating a new one.
- Behavior: The issue does not occur when printing the original PDF. It only arises after injecting custom HTML pages generated from content such as OriginalInformation, NewInformation, and CPTCodeDescription.
- SDK & Environment: We are using .NET 6.0 on a Linux App Service.
- Attachments: The specific HTML files where the rendering issue occurs have already been shared.
- Codebase Reference: The
PdfModificationHelperclass used for injecting HTML into the PDF has also been provided for your analysis.
Despite providing all necessary inputs over the last three months, we have not seen any resolution or meaningful progress. This delay has started to critically impact our timelines and deliverables.
We are escalating this issue formally and request you to assign it high priority and provide a definitive resolution timeline immediately.
Please let us know if there’s anything else required from our side—logs, sample outputs, or live session—we’re ready to support.
GenerateHtmlToPDF.zip (12.7 KB)
Thank you for providing the requested details. Please rest assured that we have been actively monitoring this issue and conducting an investigation. As mentioned earlier, we have not been able to reproduce the issue in our environment. To resolve this effectively, it is crucial for us to replicate the exact environment where you are encountering the problem. This will help us identify and address the root cause.
The API’s behavior can vary depending on different environments, as well as the specific PDFs and data provided for processing. Therefore, the details you’ve shared are essential for us to thoroughly investigate and resolve the issue. We sincerely appreciate your cooperation in supplying this information. We will now use it to continue our investigation, and as soon as we have updates to share or require further clarification, we will notify you through this forum thread. Your patience and understanding are greatly valued, and we apologize for any inconvenience caused.
I’m writing to follow up on the issue and the information we provided for your investigation, including the relevant html code and data. We appreciate your efforts in looking into the matter.
we would be grateful if you could share any updates or insights you may have regarding the resolution process. If any additional information is needed from our side to help move things forward, please don’t hesitate to let us know.
We look forward to your response.
We’re continuing to investigate the details you provided, but to pinpoint the issue, we need the original input PDF. We’re unable to reproduce the problem on our end, and having the actual file will allow us to thoroughly analyze the fonts, PDF structure, and HTML application. Could you kindly share a sample input PDF that causes the issue?
Thank you for your response and Assistance.
I’ve attached the sample PDF that triggers the issue on our end. To clarify, the error does not occur when modifying an existing PDF. it arises specifically when we add new pages generated from HTML content using HtmlFragment.
We’ve already shared the detailed code implementation along with the HTML content where the error occurs.
Please let me know if you need anything else from our side to assist in the investigation.
Sample PDF.pdf (1.2 MB)
We could not find any sample PDF attached to your post. Can you please upload it again?
Regarding the other details, we have logged it with the ticket and continue our investigation.
I’ve attached the PDF file again. kindly check and confirm if it’s received on your end.
Sample PDF.pdf (1.2 MB)
Please let me know if anything else is needed from our side.
Thanks for sharing the sample PDF. Yes, we have received it and will include in the investigation.
I’m writing to follow up on the PDF issue and the information. We would appreciate any updates you can share regarding the status of the investigation, or if there’s any additional information you require from our side to assist further.
Looking forward to your response.
The investigation is still ongoing, and we have not yet been able to reproduce the issue in our environment. It is crucial for us to replicate the exact issue on our end to provide an effective fix. Rest assured, we are actively working on the ticket. Could you kindly share the complete stack trace you are receiving? This would greatly assist us in our investigation.
Please find below the complete stack trace we are receiving related to the PDF issue. Let us know if you need any additional logs or information to assist with your investigation.
{Aspose.Pdf.FontNotFoundException: Font Arial was not found
at Aspose.Pdf.Text.FontRepository.FindFont(String fontName, Boolean ignoreCase)
at Aspose.Pdf.Artifact.get_TextState()
at Aspose.Pdf.Artifact.#=zNSeTh9dGldHG()
at Aspose.Pdf.ArtifactCollection.#=zLOULEEs2KMAh(#=zW1a77QI= #=zkcf8J6o=, List1 #=z00GHYx4=, #=zWRsGiq249Wg9xuIocIOFoMp44t3jLhwRbg== #=zkYsG$hI=) at Aspose.Pdf.ArtifactCollection.#=zDpHscLMg37N4(Matrix #=z8jBmz64=, OperatorCollection #=z2LIgdyg=, Resources #=zVmSeseI=, List1 #=zNhyLV9c=)
at Aspose.Pdf.ArtifactCollection.#=zkWzyR6g=()
at Aspose.Pdf.ArtifactCollection…ctor(Page #=ztL8V05k=)
at Aspose.Pdf.Page.#=zuB7PyrQ=(Page #=ztL8V05k=)
at Aspose.Pdf.Page.#=zPz5Jvns=(Page #=ztL8V05k=)
at Aspose.Pdf.Page.#=zQJv6Ang=(Page #=ztL8V05k=)
at Aspose.Pdf.Page.#=zgXs78r2HMnr8l10aIA==()
at Aspose.Pdf.Document.ProcessParagraphs()
at Aspose.Pdf.Document.#=z8x0DrsefZL4j(String #=znBvhdWjKP6hm, SaveOptions #=z6a7aXmg=)
at Aspose.Pdf.Document.Save(String outputFileName, SaveOptions options)
at Incisions.Incisions.PDFFileModificationHelpers.PDFModificationHelper.GetModifiedPDFWithBytes[T](GeneratePDFFormWithValuesInputModel`1 input) in /home/WAIVM41/Incisions/aspnet-core/src/Incisions.Core/Incisions/PDFFileModificationHelpers/PDFModificationHelper.cs:line 257}
Looking forward to your findings.
We will be investigating the Stack Trace and will inform you as soon as we have some findings.
Thank you for the update. I appreciate your efforts in investigating the stack trace. Please take this up as a priority and keep me informed as soon as you have any findings. Let me know if you need any additional information from my side in the meantime.
Sure, we will inform you in case we need some more information from you end. We will also notify you once we have some updates to share about ticket resolution or its fix ETA.
I’m writing to follow up on the status of the ticket. Could you please share the current progress or an estimated resolution timeline?
We would appreciate it if this could be marked as a priority, as the delay is starting to impact our internal timelines and deliverables.
Looking forward to your response.
As per our investigation against the provided stack trace, we have applied some fixes in the API. These will be part of 25.8 version which is going to be released this month i.e. August 2025. Once the API is published, you will receive a notification so that you can download and use it.
Thank you for the update and for applying the necessary fixes. I appreciate your efforts in resolving the issue. I’m looking forward to the release of version 25.8.