Doc->DOCX conversion compatibility issues

GroupDocs.Conversion Product Family
, ,
1

Hello everyone!
The following issue occurs during using GroupDocs.Convertion: by converting .doc file to .docx format the generated .docx file always has a compatibility issue
image.png (38.4 KB)
which prevent us from using the custom Word AddIns on this file… Is this possible to define the compatibility mode by the same way as for example in Aspose libraries?
Below is the code snippet with the conversion algorythm and in attachements you can find the original .doc and converted .docx files

 using (var fTemp = new FileStream(@"D:\file-sample_1MB.doc", FileMode.Open, FileAccess.Read))
{
    var loadOptions = new WordProcessingLoadOptions
    {
        Format = WordProcessingFileType.Doc
    };

    using (var converter = new Converter(() => fTemp, (LoadContext context) => loadOptions))
    {
        var options = new WordProcessingConvertOptions()
        {
            Format = WordProcessingFileType.Docx
        };

        using var fs = File.Create(@"D:\test6.docx");
        converter.Convert(options, (ConvertedContext convertedContext) =>
        {
            convertedContext.ConvertedStream.CopyTo(fs);
        });
    }
}

test3.zip (1.0 MB)

2

@atsar0621

It seems you are experiencing compatibility issues when converting a .doc file to .docx format using GroupDocs.Conversion. Unfortunately, the context does not provide specific details on how to define compatibility modes similar to Aspose libraries. However, I can suggest a few general approaches that might help you resolve the issue.

  1. Check Conversion Options: Ensure that you are using the correct conversion options. The WordProcessingConvertOptions class allows you to specify various settings for the conversion process. You might want to explore additional options that could affect compatibility.

  2. Load Options: The WordProcessingLoadOptions class can be used to specify how the source document is loaded. You can set the format explicitly to ensure that the conversion process recognizes the document type correctly. For example:

    var loadOptions = new WordProcessingLoadOptions
{
    Format = WordProcessingFileType.Doc
};

  3. Review the Output: After conversion, check the generated .docx file for any specific elements or formatting that might be causing compatibility issues. Sometimes, certain features in the original document may not translate well into the new format.

  4. Testing with Different Documents: If possible, test the conversion with different .doc files to see if the issue is consistent across all documents or specific to certain files.

  5. Consult Documentation: For more detailed information on the conversion process and available options, you can refer to the official GroupDocs documentation on converting documents, which may provide insights into handling compatibility issues.

If you continue to face challenges, consider reaching out to the GroupDocs support team or checking the forum for similar issues that other users may have encountered.

For further reference, you can check the following documentation:

If you have any more specific details or code snippets, feel free to share, and I can assist you further!

3

@atsar0621
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): CONVERSIONNET-7879

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.