EQ Field Overstrike with Image Not Rendering Properly in Aspose.Words

Aspose.Words Product Family
,
1

Description:
When processing a Word document with EQ (Equation) fields of the type {eq \o({text},\s\do55({image}))} using Aspose.Words, any shape or image positioned below the text is not rendered as expected during conversion or export.

Sample Docx:
sample.docx (19.4 KB)

Expected Result:
Images or shapes beneath the text should appear correctly, matching the original rendering in Microsoft Word. (See the attached screenshot captured from Word for reference.)

Actual Result (Aspose Output):
In the Aspose.Words output, these images (or shapes) below the text are missing or not rendered.

794×1123 644 Bytes

Code Sample:

using Aspose.Words;

new License().SetLicense($@"licensePath");
var doc = new Document($@"inputDocxPath");
doc.Save($@"outputPngPath");

Environment:

  • .NET Framework 4.8
  • Aspose.Words 25.11.0

Possible Solution:
Are there any recommended workarounds, or plans to add full support for EQ fields overlaying text and images with the overstrike \o options?

2

@chenweii

Summary
When a document contains a legacy EQ field that uses the over‑strike switch (\o) to place an image (or shape) beneath the text, Aspose.Words does not render that image part. The resulting PNG (or PDF) shows only the plain text.

Why it happens

  • The field syntax {eq \o({text},\s\do55({image}))} is a legacy EQ field.
  • Aspose.Words’ rendering engine fully supports modern Office Math (OMML) but does not implement the layout logic for the \o over‑strike option used in these old EQ fields.
  • Because the engine cannot interpret the over‑strike element, it is omitted during rendering, leaving only the textual component.

What to do next

  1. Verify that the problematic field is a legacy EQ field
foreach (Field field in doc.Range.Fields)
{
if (field.Type == FieldType.FieldEq)
Console.WriteLine($"EQ field code: {field.GetFieldCode()}");
}

This confirms the field type before applying any workaround.

  1. Check for a newer Aspose.Words build
  • Review the release notes of the latest version available to you.
  • If a newer NuGet package exists, upgrade and re‑run the conversion.
  • If the image still disappears, the limitation remains.
  1. Work‑around: replace the EQ field with a pre‑rendered picture
  • Create a picture that represents the whole equation (text + over‑strike image) – for example, by copying the equation in Word and saving it as a PNG.
  • Replace each FieldEq with a Shape that contains this picture.
using Aspose.Words;
using Aspose.Words.Drawing;
using System.Linq;

// Load the document
Document doc = new Document(@"input.docx");

// Iterate over a copy of the fields collection because we will modify the document
foreach (Field field in doc.Range.Fields.ToArray())
{
if (field.Type == FieldType.FieldEq)
{
// Path to the pre‑rendered picture of the equation
string eqImagePath = @"eqImage.png";

// Create a picture shape
Shape picture = new Shape(doc, ShapeType.Image);
picture.ImageData.SetImage(eqImagePath);
picture.WrapType = WrapType.Inline; // adjust if needed

// Insert the picture where the field was
Paragraph para = (Paragraph)field.GetAncestor(NodeType.Paragraph);
para.InsertAfter(picture, field.Start);

// Remove the original EQ field
field.Remove();
}
}

// Save the document to PNG (or PDF)
doc.Save(@"output.png");

Adjust the image path, size, and wrapping to match the original layout.

  1. Alternative: migrate the equation to modern Office Math (OMML)
  • If you can modify the source documents, replace the legacy EQ field with an OMML equation (<m:oMath>).
  • Aspose.Words fully supports OMML, so the equation—including any embedded graphics—will render correctly without additional code.
  1. Request future support
  • If rendering legacy EQ fields with the \o switch is required for your projects, raise an internal feature request through your Aspose account portal. The product team tracks such requests and may address them in a future release.

These steps should allow you to obtain the expected visual output despite the current limitation in Aspose.Words.

3

Thank you for your response.

My requirement is to fully render all equation content—including overstruck images in EQ fields—when converting Word documents to images using Aspose.Words, through a fully automated process without any manual editing in Word.

Is there currently a pure Aspose-based solution that can achieve this? If not, I hope this limitation can be considered for future enhancement, as automated processing with Aspose.Words alone is critical to my workflow.

4

Description:

Following up on the previous issue, I’d like to report another EQ field case that also fails to render correctly in Aspose.Words.
When processing a Word document with EQ (Equation) fields of the type {EQ \o(, {image})} using Aspose.Words, the overstrike formatting with combined elements is not rendered as expected during conversion or export.

Sample Docx:
sample2.docx (16.0 KB)

Expected Result (Microsoft Word Screenshot):

Actual Result (Aspose Output):

816×1056 537 Bytes

5

@chenweii
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-28826,WORDSNET-28827

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.