- Your input Word document you’re getting this problem with.
- The Aspose.Words generated output document (.docx) which shows the undesired behavior.
- Please share piece of code you used for conversion.
- What version of Aspose.Words for .NET are you currently using?
Thanks for your repy Awais Hafeez.
Thanks Awais, look forward to hearing back with a resolution soon.
Hi Awais, just checking in to see if you have any update. Thanks
Hi Awais. Anything new to report about the resolution to this problem we are having?
We have several clients that import our MS Word “DOC” files into their Medical EMR system. Their import process extracts the text from the MS Word file using a legacy proprietary program. This program is extracting the text incorrectly due to the NULL characters. This is something we have no control over.
Our clients’ import process works correctly when we use MS Word to convert the DOCX to DOC. This is because the MS Word file doesn’t contain those NULL characters from the unicode text.
We cannot use any other format other than MS Word DOC due to the legacy proprietary program that our clients use. I wish there was an alternative but there isn’t.
Is there a way that we could change that unicode text somehow to remove the NULL characters? Perhaps a method of directly modifying the bytes of the file?
Any work around is greatly appreciated until an option is added to Aspose.Words API.
Hello, just checking in to see if there might be an estimated date of when this might be corrected in the next release and what release that might be.
Just checking to see if there is an ETA to getting this implemented. Thanks, Warren