Convert to Pdf of .docx loses tracked changes

Hi,

Im converting a .docx to pdf using the converter but the tracked changes are being lost. Is there something im missing?

code:

        try
        {
            using (var docStream = File.Open(comparedFilePath, FileMode.Open))
            {
                Func<LoadOptions> loadOptions = () => new WordProcessingLoadOptions
                {
                    HideComments = false,
                    HideWordTrackedChanges = false
                };

                var converter = new GroupDocs.Conversion.Converter(() => docStream, loadOptions);

                if (!Directory.Exists(directory))
                    Directory.CreateDirectory(directory);

                PdfConvertOptions options = new PdfConvertOptions();
                converter.Convert($"{directory}\\{fileName}.pdf", options);
                var pdfStream = File.Open($"{directory}\\{fileName}.pdf", FileMode.Open);

                if (File.Exists(comparedFilePath))
                    File.Delete(comparedFilePath);

                return new PdfExportResult(pdfStream, $"{directory}\\{fileName}.pdf", $"{directory}\\{fileName}.pdf");
            }
        }

this is the end result…

image.png (9.9 KB)

expecting to see something like this…

image.png (13.1 KB)

right hand pane with an explanation of formatted changes is not shown

any help is appreciated

Thanks

@Paul.Alston

Could you please share the original .docx file where tracked changes are lost during conversion? Also specify the GroupDocs.Conversion API version that you are utilizing in the code.

I am using 23.3.1 version

Anything else you need let me know

Output2.docx (11.9 KB)

@Paul.Alston
Thanks for sharing the details. This issue is reproduced at our end. 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-6513

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.

The issues you have found earlier (filed as CONVERSIONNET-6513) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov