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

Free Support Forum - aspose.com

Conversion from DOC(2003) to PDF results in incorrect layout with Aspose.Words (.NET)

Dear Aspose Support Team,
we are experimenting an issue with .NET Aspose.Words when we convert a Word2003 doc file into pdf.
Layout in the resulting file is not correct. It is not preserved when file is converted.
In attachment you will find the original doc file and an example of converted file.
To replicate the issue you can use this simple code:

byte[] template = System.IO.File.ReadAllBytes(@"E:\Repository\Misc\AsposeTestConsole\TestDoc.doc");
try
{
    using (System.IO.Stream stream = new System.IO.MemoryStream(template))
    {
        var AsposePdfDoc = new Aspose.Words.Document(stream);


        Aspose.Words.Saving.PdfSaveOptions opt = new Aspose.Words.Saving.PdfSaveOptions() { };
        AsposePdfDoc.Save(@"E:\Repository\Misc\AsposeTestConsole\bin\Debug\" + filename + ".pdf", opt);
    }
}
catch (Exception ex)
{
    Console.WriteLine(ex.Message);
    Console.WriteLine(ex.StackTrace);
    Console.ReadKey();
}

Thank you for your kind support.AsposeDocConversion.zip (1.1 MB)emphasized text

@Fabio.Merlotti

We have managed to reproduce the same issue at our side and logged it in our issue tracking system as WORDSNET-22284. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi, I see Issue Status has been updated into Postponed. Can you please tell me what does it mean?
Thank you

@Fabio.Merlotti

Your issue is related to missing feature WORDSNET-7013 (Support “Use Word 2003 indent rules for text next to wrapped objects” compatibility option). The WORDSNET-22284 has been postponed due to this missing feature.

After the fix of WORDSNET-7013, we will look into your issues. We will be sure to inform you via this forum thread as soon as this feature is available. We apologize for your inconvenience.

The issues you have found earlier (filed as WORDSNET-22284) have been fixed in this Aspose.Words for .NET 22.5 update also available on NuGet.