Aspose.Pdf.FontNotFoundException: Font Arial was not found on Linux App Service

Thank you for the update. I appreciate you continuing to flag our concerns under the ticket. However, as this is a production issue, it is critical for us to have timely updates and a clearer understanding of the progress being made.

If there’s any additional context or an estimated timeline that can be shared, it would be greatly appreciated. Please keep us informed of any developments as soon as they arise.

@vishalbh

The ticket is sadly not fully investigated as it has been logged recently under free support model. There are other issues in the queue that were logged prior to this ticket and we are checking them at the moment. As per free support policies, the ticket has normal priority and will be resolved on a first come first serve basis. We have been recording your concerns and raising them internally as well and as soon as some progress is made, we will inform you. We apologize for the inconvenience.

Thank you for the update.

I understand the constraints of the free support model and appreciate you taking the time to acknowledge the ticket. I’m glad to hear that our concerns are being recorded and raised internally. We’ll wait for further updates and trust that you’ll inform us as soon as there’s any progress.

Thanks again for your assistance.

@vishalbh

We are afraid that no progress has been made yet. You will be informed as soon as there are some news in this regard. We apologize for the inconvenience.

Thank you for your previous update. However, as the matter remains unresolved and is impacting our operations, I would like to kindly request that this ticket be treated as a priority.

We would greatly appreciate any efforts to expedite the resolution process and would be grateful for a prompt update on the current status.

Please let us know if any additional information is needed from our side to assist in moving this forward.

Looking forward to your response.

@vishalbh

Since the ticket has been logged under free support model, we can only escalate it to a certain level of priority (not the highest which comes along with paid support). We have already logged your concerns and raised them internally. Sadly, no progress has been made yet in this regard due to other high priority issues in the queue. As soon as we have some news or ETA, we will share with you.

We apologize for the inconvenience.

Thank you for your response and for raising the issue internally.

I understand the limitations of the free support model and appreciate your efforts so far. However, since the issue remains unresolved and is impacting our operations, I’d like to kindly follow up and check if there have been any updates or if an estimated timeline for resolution is now available.

We value your support and would appreciate any information you can share regarding the progress or next steps.

Looking forward to your response.

@vishalbh

Sadly, we have not been able to make any progress yet. Once we make some progress towards ticket resolution or have we any updates about ETA, we will let you know. Your patience is appreciated in this matter.

Thank you for the update.

While awaiting further progress, we’d like to highlight a specific issue we’ve encountered during PDF generation which might help in resolving the ticket faster.

We’ve identified that the following lines in the ExtractAuditLogChanges method appear to be at the root of the issue:

OriginalInformation = GetPropertyChangeValue(logEntry.OriginalInformation, logEntry.FieldChanged),
NewInformation = GetPropertyChangeValue(logEntry.NewInformation, logEntry.FieldChanged)

The problem specifically arises when the content returned in OriginalInformation or NewInformation is large and placed inside a <td> cell. When this content is rendered inside a <td> element, it might causes broken HTML rendering due to content overflow, and subsequently, the PDF generation fails with the error:
“font Arial was not found”.

We’ve already attempted to resolve this by reducing padding and font size within the HTML style and it worked for some records , but the issue still persists when handling large text blocks for other records. It seems that under these conditions, the renderer defaults to Arial or requires font fallback behavior, which leads to the failure since Arial is not embedded or available.

For reference, we’ve attached the full method implementation as ExtractAuditLogChanges.zip.

Please let us know if further input or sample data is needed from our side.

Appreciate your continued support on this.
ExtractAuditLogChanges.zip (1.3 KB)

@vishalbh

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.

@vishalbh

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 PdfModificationHelper class 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)

@vishalbh

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.