While performing recursive conversion of container file formats, e.g. in these 3 samples:
Convert PST or OST documents to different formats | Documentation (groupdocs.com)
Convert each email attachment to different format | Documentation (groupdocs.com)
Convert each email attachment to different format | Documentation (groupdocs.com)
Is it possible to also intercept each of the constituent files that are converted so that we can save out copies of the native constituent files?
@jarrodwee
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-6831
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.
Thanks, will create a new ticket in the Paid Support.
Additionally, the original filenames of the native constituent files will be required for setting the filenames of the native and converted files.
The issues you have found earlier (filed as CONVERSIONNET-6831) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov
We are investigating this, your investigation ticket ID is TOTALNET-72. You’ll be notified in case of any update.
The issues you have found earlier (filed as TOTALNET-72) have been fixed in this update. This message was posted using Bugs notification tool by yevgen-nykytenko
Reopening under free support for additional lower priority issues discovered in Paid Support ticket #004597 “Saving native constituent files during conversion?” so as to conserve paid ticket quota.
Sample test files and test program code to reproduce the issues were previously attached in the Paid Support ticket above - do let me know if I need to reattach them in this forum as well.
Issue #1:
Issue #2:
Could you please share source files and the code here as well? Also specify GroupDocs.Conversion for .NET API version that is causing the issue.
I’m using GroupDocs.Total.NETFramework 24.8 but the issues should be reproducible in GroupDocs.Conversion for .NET 24.8 too.
Sample MS Word Document and Source code attached herewith:
test.docx (30.2 KB)
Program-20240906.zip (1.1 KB)
Please take a look at this output.png (52.9 KB).
Are you saying that the embedded documents cannot be opened or they fail to open upon clicking?
We observed that the filenames remain unchanged in both the PDF and the Word file. They stay the same.
The recent GroupDocs.Conversion convert function is able to recursively auto-extract and convert embedded files for MS Office and PDF file types.
Your image shows the embedded Word document icon (with correct filename) within the parent document. Using the new convert capability, GroupDocs is now able to auto-extract and convert the embedded Word document. However, the filename of the extracted and converted files are not named correctly.
For the text files embedded in Word document, the extracted and converted files are corrupted.
Note that these two issues have been confirmed reproducible by your colleagues under the Paid Support ticket #004597 “Saving native constituent files during conversion?” but need to be raised as separate new issues in the tracking system - under free support to conserve quota.
@jarrodwee
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-7138
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-7138) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov
Any indication of when NuGet Gallery | GroupDocs.Total.NETFramework 24.8.0 will be updated with the latest components?
GroupDocs.Total for .NET 24.9 was published:
Have a nice day!