We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

ASPOSE DOCX to ODT error

Hi support team,
We use JAVE in RedHat Enterprise Linux 8.0,Aspose is 18.1 (aspose-words-18.1.jar)
This is word report.
A.png (107.5 KB)
This is ODT/ report
B.png (141.7 KB)
this is code sample from website.
C.png (41.9 KB)
QIK160P_file shows that the formatting is off.
QIK160P_.zip (28.2 KB)

Peggy

@accesssoft Please explain what exactly in the screenshot you consider a conversion error: differences in pages layout in the initial and the final document, table borders display or something else? Please also attach the expected version of the output document and inform us which editor you are using to view the Odt file.

Let me explain what exactly in the screenshot you consider a conversion error: differences in pages layout in the initial and the final document, table borders display or something else? "

  1. The initial document in WORD format (1st screenshot) has correct 2nd page title information on the 2nd page header as indicated in red box.
    A.png (107.5 KB)

  2. The final converted document in ODT format (2nd screenshot) has 2nd page title information on the bottom/footer of the 1st page. This is is the conversion error.
    B.png (141.7 KB)

“Please also attach the expected version of the output document and inform us which editor you are using to view the Odt file.”

  1. The expected version of the output document in ODT format (3rd screenshot) should have each page title information on each page header.

C.png (126.9 KB)

  1. Any open office writer (Libre, NDC, Apache) all have the same issue.

@accesssoft I saved “QIK160P.docx” to “QIK160P_word.odt” using MS Word 2019 and saw the following layout:

I opened “QIK160P.docx” in Libre Office and saw the following layout:

Thus, the layout provided by Aspose.Words is completely similar to what MS Word 2019 and Libre Office show.
As for the original “QIK160P.docx”, the page numbers pointed in screenshots are not fields, but plain text that will correctly show the page numbers only if the approach to page composition in Docx and ODT is the same, which is not the case.
If you expect pages in Docx and ODT to break at the same place, you shall insert a page break character at that place, only then the pagination of the documents will be the same. I attach the Docx document containing correctly placed PageBreak(-s).
QIK160P_WithBreaks.docx (12.3 KB)

Hi Peggy,

Thank you for your support.

Our client can open QIK160P_WithBreaks.docx file. We can see vender add page break at DOCX.
A.png (169.0 KB)

While our client use WORD 2013to converting DOCX to ODT file. It is no problem while page break.

But if they don’t use Page Break, it cause layout incorrect.

  1. DoCX has normal page breaks without adding page breaks (page breaks), and it will run the version by running through Aspose. How to resolve the problem?

  2. If you add a page break symbol (page break), you can run the version through aspose’s file conversion, then the correct page break symbol that can be used in jasperreport can produce a DOCX with a page break symbol (page break). ?

Attached is JRXML with page break (page break) addedb.png (173.0 KB)

https://www.dropbox.com/s/9kdll76y38jot10/QIK160P.jrxml?dl=0

@accesssoft Thank you for additional information. But you should note that both DOCX and ODT documents are flow documents and their appearance depends on the consumer application used to view the documents. This like different Web browsers can display the same HTML differently.
Also, since DOCX and ODT are different format by their document model it is not always possible to get 100% fidelity after conversion from one format to another.

it sees tat you doesn’t answer our questions*

  1. DoCX has normal page breaks without adding page breaks (page breaks), and it will run the version by running through Aspose. How to resolve the problem?
  2. If you add a page break symbol (page break), you can run the version through aspose’s file conversion, then the correct page break symbol that can be used in jasperreport can produce a DOCX with a page break symbol (page break). ?

@accesssoft

  1. Your question is not quite clear. MS Word as well as ODT documents are flow documents and does not have a page concept. Content of the document is layout into pages on the fly by the consumer application. So depending on the consumer application and the fonts available in the environment page layout might differ.

  2. You can configure page breaks behavior in Jasper Reports as it is described here;
    https://docs.aspose.com/words/jasperreports/page-breaks/

Hi George,
Our customers have encountered problems in use,
Can you please help to answer?


For the web page information you provided in point 2, there is an import component

com.aspose.words.jasperreports.*;

We checked the currently used ASPOSE library, and it seems that there are no related components of jasperreports.

The ASPOSE webpage has the version number of JasperReports and the corresponding JAR file version.

The ASPOSE WORD library we are currently using is 18.1, but the version of jasperreports is 6.19.

Finally, what we want to ask is whether ASPOSE can provide the corresponding or
latest version of ASPOSE library containing jasperreports for us to test to see if it can solve the pagination problem?

Thank you.

Peggy

@accesssoft Aspose.Words for JasperReports is a separate product it is not a part of Aspose.Words for Java. You can download the latest version of Aspose.Words for JasperReports from here:
https://releases.aspose.com/words/jasperreports/
It can be used with JasperReports 6.0 or higher. Please see our documentation for more information:
https://docs.aspose.com/words/jasperreports/system-requirements/

We referenced sample code and evaluated the jar (aspose.words.jasperreports-22.11.0-7.8.0-8.0.0.jar) from the latest release. It seems the page title (QIK160P_20.11) or page header (QIK182P_20.11) is missing. Here I also attach the original docx (not using the library) for your reference.

We are using JasperReports 6.19.x as we informed in previous email, and we did not find a corresponding aspose.words.jasperreports-xxx.jar in readme as below:

We would like to know the issue that causes page title or header missing using the library, and also we need to request a temporary license as the link below to fully evaluate on JasperReport library. Please let us know what to do to move forward on the issue and getting the temporary license.

https://purchase.aspose.com/temporary-license/

@accesssoft

  1. Could you please create a standalone application that will include all required resources and allow us to reproduce the problem. Unfortunately, your workflow is not clear enough.

  2. Please use this JAR for JasperReports 6.19.x. We have tested it and it works fine up to 6.20 version. We will update readme file in the next release.

For JasperServer	For JasperReports	Use following JAR library
----------------	-----------------	-------------------------
7.8.0 ... 8.0.0 	6.12.0... 6.18.1	aspose.words.jasperreports-22.11.0-7.8.0-8.0.0.jar
  1. Please just follow the steps described here to get the temporary license.

Hi Alexey,

Our current method is also to directly output docx from the jasperreport library provided by .jasper through Original Design Manufacturer.

And because the project data has security-sensitive considerations,
The customer is asking whether it is enough to provide the .jrxml and the compiled .jasper report to the Original Design Manufacturer for testing?

This customer thinks that as long as they test directly from their report, others can see that the output docx file will have titles or headers missing.

A.7z (13.0 KB)

@accesssoft Thank you for additional information. Please correct me if I am wrong, the report is exported to DOCX without using Aspose.Words using built-in JarperReports capabilities and the produced DOCX document already has the described problem, i.e. missed titles and headers. If so, if the problem occurs after exporting report to DOCX and before processing the document with Aspose.Words, it is not quite clear how the problem is related to Aspose.Words.