Hi Chase,
Thanks for sharing the detail.
apatter:
The biggest issue: vsdx file is corrupted. It looks like the compound binary file contains an OOXML file called Package. If I extract the Package and append the “.vsdx” extension, the file will open correctly, though it is a hassle.
I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of
correction, I have logged this problem in our issue tracking system as WORDSNET-10589. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.
apatter:
This seems to be similar to an issue I noticed with “.xlsm” files in version 13.5.0.
I have not found this issue using the shared code. I have attached the output xlsm file with this post for your kind reference.
apatter:
The rtf file was converted into what appears to be the “.doc” format. It does open okay and has the correct contents. Is there a reason this is converted to a “.doc”?
The rtf.rtf document have embedded Doc contents. Please check this embedded object using MS Word.
apatter:
For the vsdx file, the suggested extension is ".bin"
I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-10590.
apatter:
For the dot (Microsoft Word Document Template), it the suggested extension is “.doc”. The file appears to open in Word regardless of whether it is set as “.doc” or ".dot"
I have tested the scenario and have managed
to reproduce the same issue at my side. For the sake of correction, I
have logged this problem in our issue tracking system as WORDSNET-10591.
We apologize for your inconvenience.