Hello
Can you please be so kind and check this rar file sample, which is wrongly detected as TEXT?
Just please unzip and get the real .rar sample inside.
PID 9.zip (7.4 MB)
Detecting Text is a very hard task, better to share the algorithm with other components like Cells etc…
@australian.dev.nerds
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): WORDSNET-26038
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.
PS: If try to open the attached RAR file using MS Word, it also detects it as TXT document.
1 Like
Thanks, I understand you need to mimic the original behavior as much as possible, but not when the original action has a bug or not wise, logically!
Furthermore, one usage is just to detect file format, not to pass it to internal load format.
@australian.dev.nerds Aspose.Words is designed to work with MS Word documents at first and FileFormatUtil
is intended to detect file formats which are supported by Aspose.Words as load file formats. RAR is not among them and you are absolutely right, it should be detected as Unsupported
file format instead of TXT. We will fix this in one of future versions.
1 Like
Thanks, just one thing, I’ve tested it against many rar files, only this rar file was detected as TEXT.
I’ve no idea how the underlying code goes, but seems not checking the magic numbers.
Also binary files shall not be detected as text, csv etc…
@australian.dev.nerds We will investigate the issue and let you know once it is resolved.
PS: CSV is actually TXT format, it is not binary format.
The issues you have found earlier (filed as WORDSNET-26038) have been fixed in this Aspose.Words for .NET 24.11 update also available on NuGet.