Hi,
We are having an issue regarding inflated PDF sizes when comparing this with equivalent rendering using the older "Tools SDK". We have reason to believe this has something to do with embedded fonts, which always seem to be embedded into the PDF even if we use "FontPolicy_Never" as the font policy. We are using EMF as the source document and thus the "ConvertMetaFile" method.
I have attached a sample project that illustrates our problem.
Could you help us with this and do you know of any other approaches to reduce file sizes to be inline with those of the v4 "Tools SDK"? We are comparing equivalent settings such as compression etc. Here are some figures for a single page sample, first column is "v4 Tools SDK" second column is "v6 Core SDK":
Jpeg high quality - 160Kb - 360Kb
Jpeg medium quality - 65Kb - 254kb
Jpeg low quality - 47kb - 235kb
Any help is gratefully received,
Richard.
Increased PDF sizes when compared with v4 "Tools SDK"
Moderators: TrackerSupp-Daniel, Tracker Support, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Tracker Supp-Stefan
Forum rules
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
-
- User
- Posts: 6
- Joined: Tue Jul 13, 2010 8:54 am
Increased PDF sizes when compared with v4 "Tools SDK"
You do not have the required permissions to view the files attached to this post.
-
- User
- Posts: 5522
- Joined: Fri Nov 21, 2014 8:27 am
Re: Increased PDF sizes when compared with v4 "Tools SDK"
Hello Richard,
The EMF functionality was changed and if there are glyphs inside then the font will be embedded.
Cheers,
Alex
The EMF functionality was changed and if there are glyphs inside then the font will be embedded.
Cheers,
Alex
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
-
- User
- Posts: 6
- Joined: Tue Jul 13, 2010 8:54 am
Re: Increased PDF sizes when compared with v4 "Tools SDK"
Hi Sasha,
Thank you for your reply. Is there anything we can do to bring the PDF sizes more inline with V4 Tools SDK?
Our product processes 1000s of documents at a time and we believe the increased file size is having an impact on performance.
Thank you for your reply. Is there anything we can do to bring the PDF sizes more inline with V4 Tools SDK?
Our product processes 1000s of documents at a time and we believe the increased file size is having an impact on performance.
-
- Site Admin
- Posts: 17949
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
Re: Increased PDF sizes when compared with v4 "Tools SDK"
Hello Richard,
I've just spoken with a colleague from the dev team and he has advised that a better approach to utilizing the new SDK would be to avoid the EMFs and instead use IPXC_ContentCreator interface directly.
For example when the EMF conversion is utilized - the same settings are used for all images inside.So if there are e.g. a screenshot and a photo in the same file - you have to decide between screenshot quality or file size, while if EMF is avoided - you can have a higher quality for the shot, and lower for the photo. The direct using of the SDK interfaces instead gives much more control over image insertion (you can change conversion rules for each image individually if needed), font usage, transparency, etc. This can reduce file size and preserve quality where it is needed at the same time.
Regards,
Stefan
I've just spoken with a colleague from the dev team and he has advised that a better approach to utilizing the new SDK would be to avoid the EMFs and instead use IPXC_ContentCreator interface directly.
For example when the EMF conversion is utilized - the same settings are used for all images inside.So if there are e.g. a screenshot and a photo in the same file - you have to decide between screenshot quality or file size, while if EMF is avoided - you can have a higher quality for the shot, and lower for the photo. The direct using of the SDK interfaces instead gives much more control over image insertion (you can change conversion rules for each image individually if needed), font usage, transparency, etc. This can reduce file size and preserve quality where it is needed at the same time.
Regards,
Stefan