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

Free Support Forum - aspose.com

Widow and orphan control setting not respected in Word conversion?

Hello,



It seems that, when converting RTF files to .doc or .docx format, Aspose always turns on widow and orphan control, even if the RTF file does not ask for this. We have tested with RTF documents that have the “\widowctrl” tag and RTF documents that don’t, and all of them come out with widow and orphan control when converted to .doc or .docx. (If we open the original RTF files in Word, there is no widow and orphan control if there is no “\widowctrl” tag; but the converted .doc and .docx files have widow and orphan control regardless.)



Many thanks,

Keith

Hi Keith,


Thanks for your inquiry. Could you please attach your 1) input Word documents (.rtf file), 2) Aspose.Words generated output Word documents (.doc/.docx files) and 3) MS Word generated .docx files here for testing? We will investigate the issue on our end and provide you more information.

Best regards,

Hi Awais,



Sorry for the late reply; I’ve been on holiday. Attached is a .zip file containing the files you requested - an input RTF file, and two .docx files, one created by piping the RTF file through Aspose, and the other created by opening the RTF file in Word and saving as a .docx. If you view these documents in Word (using A4 paper size), you should see several widows and orphans in the RTF file and in the Word-generated .docx file, whereas the Appose-generated .docx file avoids widows and orphans.



All the best,

Keith

Hi Keith,


Thanks for your inquiry.

While using the latest version of Aspose.Words i.e. 15.7.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-12308. Your thread has been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,

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


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