-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve backend resolution logic #802
Comments
It turns out also the |
As discovered in #542, some MS Office XML archives have the meta file One way of improving the logic could be:
|
Another sample of a word document not detected as such is seen in issue #476. |
I'm seeing this issue for pptx files where
And the subsequent
Finally, I hope this is helpful, here is a
|
Requested feature
Document conversion currently contains a logic for "guessing" / resolving the backend to use for a given input (ref).
This logic has some limitations, e.g. when working with streams, it relies on the first 8KB to detect the backend to use — which may or may not be enough for a correct detection (e.g. deciding info could only appear at the end of a 10KB stream).
Consider ways to remove these limitations.
One possible high-level approach to examine could be to:
The text was updated successfully, but these errors were encountered: