Issue with Symbol Rendering after Formatting Change in Tracked Changes – Aspose.Words for .NET

Aspose.Words Product Family
1

Hello,

we are encountering a rendering issue when converting a Word document to PDF using **
Example Dok1_Aspose.docx (14,7 KB)

Example Dok1_Aspose_gerated with Aspose (with error).pdf (74,7 KB)

**. The problem specifically occurs under the following conditions:

  1. A special symbol (e.g. Unicode U+F06D, often used from symbol fonts) is inserted into the Word document.
  2. Track Changes is enabled in the document.
  3. The symbol is copied and subsequently formatted (e.g. bold, italic, underline).
  4. When exporting this document to PDF using Aspose.Words, the symbol is incorrectly rendered or replaced by a placeholder.
  5. The issue does not occur:
  • if the symbol is formatted without tracked changes,
  • or if the symbol is copied while tracked changes are active but not additionally reformatted afterward.
  • or if the font is changed to Aptos manually before export.
  • or when exporting to PDF using Microsoft Word’s built-in exporter or other tools.

We assume the problem may relate to how Aspose handles font fallback or symbol rendering in combination with tracked formatting changes.

To illustrate the issue, I have attached:

  • Example Dok1_Aspose.docx - the original test document with the tracked change and symbol formatting
  • Example Dok1_Aspose_gerated with Aspose (with error).pdf - the result of converting the same file using Aspose.Words for .NET

Please advise if this is a known issue or if there’s a workaround (e.g. font embedding, substitution configuration). Also, is there any plan to improve symbol handling in such cases?

Thank you in advance.

2

@agu67

Cause

The rendering issue you’re experiencing when converting a Word document to PDF with Aspose.Words is likely due to how the library handles special symbols, especially those formatted with tracked changes. This can result in incorrect rendering or placeholders appearing instead of the actual symbols.

Solution

To resolve this issue, please follow these steps:

  1. Font Embedding: Ensure that the font used for the special symbols is embedded in the PDF. This will help prevent rendering issues related to font availability.

  2. Use Unicode Fonts: If feasible, replace the special symbols with characters from a Unicode font that is more reliably supported, such as “Segoe UI Symbol”. This can help avoid issues with symbol fonts that may not render correctly.

  3. Export Options: Adjust the PDF export options to ensure that the document structure is preserved. Utilize the PdfSaveOptions class to specify compliance levels and other settings.

  4. Track Changes Handling: If the issue persists, consider disabling track changes for the specific formatting of the symbols, if possible. This may assist in rendering them correctly.

Code

Here’s a sample code snippet to set the PDF export options and ensure font embedding:

Document doc = new Document("path/to/your/document.docx");
PdfSaveOptions saveOptions = new PdfSaveOptions
{
    Compliance = PdfCompliance.PdfA1, // or PdfUa1 based on your needs
    EmbedFullFonts = true // Ensure fonts are embedded
};

doc.Save("path/to/output/document.pdf", saveOptions);

Next Steps

  1. Test the above code with your document to determine if it resolves the rendering issue.
  2. If the problem persists, reach out to Aspose support with detailed information about the symbols and formatting used in your document.
  3. Monitor updates from Aspose regarding improvements in symbol handling, particularly in relation to tracked changes.

Please let me know if you need further assistance!

3

@agu67
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-28407

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.