1. Open attachment 102363 [details]
2. Save as a new .DOCX file
3. Open then new file in MSOffice
Observed behaviour: file is corrupted
Build ID: 757a60d01dd152aadab2ba3c8224252481ce8a88
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout
Locale: ca-ES (ca_ES.UTF-8); Calc: group
but not in
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Regression introduced by:
author Heena Gupta <firstname.lastname@example.org> 2014-09-03 12:27:47 (GMT)
committer Muthu Subramanian K <email@example.com> 2014-09-07 16:37:59 (GMT)
commit 47c5454ea67632278d69a1ddfe97d74f5cc4449f (patch)
parent 1b02831d802ab8327a4b73528c7200289f2a0279 (diff)
fdo#83428: Custom Properties dropped while exporting to docx
Adding Cc: to Heena Gupta
Error displayed by Open XML SDK 2.5:
1. CustomDocumentProperty: Attribute 'name' should have unique value.
2. DocGrid: The attribute main:charSpace has invalid value '4294965247'. The string '4294965247' is not a valid 'Int32' value
How can I verify OOXML document by using Open XML SDK 2.5?
Do you have any tutorial how to configure it?
You just download the GUI program on Windows, open the docx file and there is a "validate" button to see errors.
I downloaded OOXML SDK from webpage:
but I cannot find any application for validation.
The SDK contains the following (taken from documentation):
- Readme.htm (this file)
- API: (DocumentFormat.OpenXml.dll)
- Intellisense: (DocumentFormat.OpenXML.xml
I need to run it to resolve OOXML bugs. Thanks
On that site you can download the SDK (smaller file) and the SDK Productivity Tool (larger file), did you install the later as well? That's what provides the GUI tool to validate OOXML files according to MS schemas. I think it creates an icon on the desktop after installation.
The SDK Productivity Tool is no longer available to download, even if it is visible to to download. It is always download smaller "Open XML SDK". After downloading it from external resource, it is installed correctly.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!