-
Notifications
You must be signed in to change notification settings - Fork 2
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
Excel display in demos differs greatly from expected display #53
Comments
The online Viewer uses new version of Angular UI that is going to replace the current one. And renders files to PNG instead of HTML so the output looks different. You can configure this demo to work the same using the following code in
Also you can give a try a complete application - sample-app.zip. |
@vladimir-litvinchik This works perfectly. Thank you very much! |
You're welcome! Unfortunately, changing the output type from HTML to PNG is not possible in the current implementation. The packages were designed in a way where all the configuration is set once during application startup. Also, client-side Angular application is depends on this config. |
I understand. With the ViewerType.Png option, pdf documents are sometimes rendered blurred and unattractive. Text passages can also not be marked etc. |
Can you please attach the PDF file that you're opening? We'll take a look at how we can improve the output. |
Our customers tell us that the display of Excel documents sometimes differs greatly from the expected display.
I have therefore compared your ASP.NET Core demo with your online viewer at https://products.groupdocs.app/viewer/total.
Your online viewer displays Excel documents much more adequately than the demo (on which we have based our integration).
Below are two screenshots of a sample document that I have attached to this ticket:
Test.xlsx in ASP.NET Core demo:
Test.xlsx in online viewer:
How can I configure GroupDocs Viewer so that Excel documents are displayed in the same way as in your online viewer?
Test.xlsx
The text was updated successfully, but these errors were encountered: