Unfortunately it seems that the update fields is failing due to this MathML:
import com.aspose.words.Document;
import com.aspose.words.DocumentBuilder;
public class AsposeCase5418 {
static String testCase = "<math xmlns=\"http://www.w3.org/1998/Math/MathML\">\n"
+ "<mtable columnalign=\"left\" rowspacing=\"4pt\" columnspacing=\"1em\">\n"
+ " <mtr>\n"
+ " <mtd>\n"
+ " <mrow>\n"
+ " <msqrt>\n"
+ " <mrow>\n"
+ " <mn>3</mn>\n"
+ " </mrow>\n"
+ " </msqrt>\n"
+ " </mrow>\n"
+ " </mtd>\n"
+ " </mtr>\n"
+ "</mtable>\n"
+ "</math>";
public static void main(String[] args) {
String dataDir = "./";
// Load the document.
Document doc;
try {
doc = new Document();
DocumentBuilder builder = new DocumentBuilder(doc);
builder.insertHtml(testCase);
try {
doc.updateFields();
doc.updatePageLayout();
} catch (Exception e) {
System.err.println(e.getMessage());
System.err.println("Unable to update fields.");
doc.save(dataDir + "output.docx");
}
doc.save(dataDir + "output.docx");
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}
The same exception can also be reproduced with the code snippet from this topic:
https://forum.aspose.com/t/mathml-with-missing-elements-and-word-document-corrupted/263469
Any idea how to fix this? Unfortunately it affects any Table of Contents because without the update fields, all page numbers show “?” instead of the actual page number.
@Mmachado
It seems that you are encountering an issue with updating fields in a document that contains MathML. The exception you are facing may be related to how Aspose.Words processes MathML content, which can sometimes lead to complications when updating fields, especially for elements like tables of contents.
To address this issue, you can try the following steps:
-
Ensure Proper MathML Structure: Verify that the MathML you are inserting is well-formed and adheres to the expected structure. Any missing or incorrectly formatted elements could lead to issues during the field update process.
-
Update Fields After Insertion: Make sure to call the updateFields()
method after inserting the MathML content. This ensures that all fields, including those related to page numbers, are updated correctly.
-
Check for Unsupported Elements: Some MathML elements may not be fully supported by Aspose.Words. If possible, simplify the MathML content to see if that resolves the issue.
-
Use Try-Catch for Debugging: Since you are already using a try-catch block, consider logging the specific exception message to get more insight into what might be going wrong. This can help in diagnosing the issue further.
-
Consult Documentation: Review the Aspose.Words documentation regarding field updates and MathML support. This can provide additional insights into any limitations or specific requirements for using MathML with Aspose.Words.
If the problem persists, you may want to reach out to the Aspose support team with the specific error message you are receiving, as they can provide more targeted assistance.
For further reading, you can check the following resources:
These documents provide detailed information on how fields are managed and updated within Aspose.Words, which may help you troubleshoot the issue more effectively.
@Mmachado Unfortunately, I cannot reproduce the problem on my side using the latest 24.9 version of Aspose.Words. Here is output document produced by the following code:
String testCase = "<math xmlns=\"http://www.w3.org/1998/Math/MathML\">\n"
+ "<mtable columnalign=\"left\" rowspacing=\"4pt\" columnspacing=\"1em\">\n"
+ " <mtr>\n"
+ " <mtd>\n"
+ " <mrow>\n"
+ " <msqrt>\n"
+ " <mrow>\n"
+ " <mn>3</mn>\n"
+ " </mrow>\n"
+ " </msqrt>\n"
+ " </mrow>\n"
+ " </mtd>\n"
+ " </mtr>\n"
+ "</mtable>\n"
+ "</math>";
Document doc = new Document();
DocumentBuilder builder = new DocumentBuilder(doc);
builder.insertHtml(testCase);
doc.updateFields();
doc.updatePageLayout();
doc.save("C:\\Temp\\out.docx");
out.docx (7.3 KB)
1 Like
Hello Alexey,
Thank you for checking out this issue.
Only after creating the topic did I go back and check our aspose version. Your statement is correct, this issue seems to be resolved in version 24.9.
For furture reference, we were using version 23.7
Regards,
1 Like