2010 documents move to "compatibility mode" after being opened in Aspose.Words

Aspose.Words Product Family
1

Hi,

Documents created in Word 2010 seem to be changed into some kind of “compatibility mode” after they have been opened in Aspose.Words.

This is indicted on the title bar of Word when it re-opens the document.

Best regards

Martin

2

Hi

Thanks for your inquiry. I think, you should just specify OOXMLCompliance:
https://reference.aspose.com/words/net/aspose.words.saving/ooxmlcompliance/

Here is code example:

Document doc = new Document(@"Test001\in.docx");
OoxmlSaveOptions opt = new OoxmlSaveOptions(SaveFormat.Docx);
opt.Compliance = OoxmlCompliance.Iso29500_2008_Transitional;
doc.Save(@"Test001\out.docx", opt);

Please let me know if this helps.

Best regards.

3

Thank-you - this is very useful.

Is there a way, within Aspose.Words, to find out if the document that was loaded is in ECMA-376 1st Edition or ISO/IEC29500 Transitional format? This would then allow me to set the compliance option on saving.

Thanks

Martin

4

Hi

Thanks for your request. Unfortunately, there is no way to determine whether the loaded document was in ECMA-376 1st Edition or ISO/IEC29500 Transitional format. You can only determine whether the loaded document was DOCX document:

https://reference.aspose.com/words/net/aspose.words/document/originalloadformat/

Best regards,

5

Hi,

I think there is a bug in this flag.

When I save a document using this flag, Word 2010 complains that the word/settings.xml file is corrupt. This seems to be because an XML namespace is not being used.

The contents actually looks like this:

  <w:compat>
    <compatSetting name="compatibilityMode" uri="http://schemas.microsoft.com/office/word" val="14" />

But should look like this:

  <w:compat>
    <w:compatSetting name="compatibilityMode" uri="http://schemas.microsoft.com/office/word" val="14" />

Is this is a bug?

Thanks

Martin

6

Hello Martin,

Thank you for reporting this problem to us. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is fixed.

Best regards,

7

Hi,

Is it possible for you to add a property to determine 2007/2010 within Aspose.Words? I’ve been trying to work out how we could determine this in our code and it would be extremely difficult.

Thanks

Martin

8

Hi Martin,

Thanks for your request. We will consider adding this functionality. Your request has been linked to the appropriate issue. You will be notified as soon as it is supported.

Best regards,

9

Hi,

Is there already a solution for this bug?

Best regards,

Joost

10

Hi

Thanks for your request. Unfortunately, the issue is still unresolved. I will let you know once there is something new regarding this issue.

Best regards,

11

Hi Andrey

Maybe I got the same issue. If we merge some files in a “Word (compatibility mode)” file, we want save the file in comp. mode. If not, it should not be saved in compatibility mode. In case of that, we have to find out what mode the file was.

I hope it will be implemented soon.

Thanks

Martin

12

Hello.

Thank you for your request.
Could you please provide us your input document for testing? We’ll check it on our side and only after testing able to say, is it the same situation as described above or not.

13

Hi Aspose Team

I tried OoxmlCompliance.Iso29500_2008_Transitional feature but generated docx files are still in [compatibility mode] in Office Word 2010.

Aspose.Words.Document doc = new Document();
DocumentBuilder db = new DocumentBuilder(doc);
db.CurrentParagraph.Runs.Add(new Run(doc, "some text"));
OoxmlSaveOptions SaveOption = new OoxmlSaveOptions(SaveFormat.Docx);
SaveOption.Compliance = OoxmlCompliance.Iso29500_2008_Transitional;
doc.Save(@"C:\Users\venayre-m\Desktop\out.docx", SaveOption);

Result file is in attachment

I’m using Microsoft Office Professionnel PLus 2010
14.0.5128.5000 (32 bits)

Is there something else to avoid [compatibility mode] ?

Thanks

14

Hello

Thank you for reporting this problem to us. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved.

Best regards,

15

The issues you have found earlier (filed as WORDSNET-3760) have been fixed in this .NET update and in this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
16

The issues you have found earlier (filed as WORDSNET-4777) have been fixed in this .NET update and in this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
17

The issues you have found earlier (filed as WORDSNET-6410) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
18

The issues you have found earlier (filed as WORDSNET-3762) have been fixed in this Aspose.Words for .NET 16.10.0 update and this Aspose.Words for Java 16.10.0 update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(9)