This Forum is for the use of Software Developers requiring help and assistance for Tracker Software's PDF-Tools SDK of Library DLL functions(only) - Please use the PDF-XChange Drivers API SDK Forum for assistance with all PDF Print Driver related topics or PDF-XChange Viewer SDK if appropriate.
This works well except for some PDF documents, there matrix.e and matrix.f are zero (everything is zero except scaling .a and .d are 1) for every element in the document.
quick offtopic question,
as far as I know we are not notified of new builds.
Is there a mailing list or something like that?
We would like to addopt this new build once its released
Yes - if you have an account on our website - you can subscribe for our newsletter, and monthly e-mails. The new build (#200) is planned for mid December as far as I know at this point.
We released build 200 last night, so please do check if your second problem is also resolved, and if it is not - please do consider sending us the sample file - and we will see to get this resolved in the next build.
The second problem of offset zero for all elements still occurs (build 200 and 201).
Attached is an example document, striped down to the bare basics (but the entire original pdf had this problem) to reproduce this problem.
When we process the element acquired with PXCp_ET_GetElement we get offset 0 for all characters.
Mask used: PTEM_Text | PTEM_Offsets | PTEM_Matrix | PTEM_TextParams | PTEM_FontInfo
Try the "healthcare" text and it returns all 0's for all character offsets.
We've created a ticket for this case and a developer has been assigned: #1452: PXCp_ET_GetElement returns 0 for position
and will try to resolve it as soon as possible. We will update this topic when there is any further info.
Do you have any idea on what the cause is of this problem.
The reason I'm asking is, since this happens only with some documents, might there be a temporary work around, till you resolve this?
I'm guessing that the way this PDF was created is giving some problems, might there be specific settings when generating the original PDF that could avoid this problem?
note that this particular document was not generated with your tools.
Yes it's quite possible that there is something specific to the file that is causing this.
Our ticketing system is temporary offline - so I can't check the latest comments in there - but as soon as it's back on - I will see to post an update here.
Hello Marco.
There is problem in your file (not critical for viewing or text ectraction) and xcpro was not avble to handle it correctly. According to PDF specification Font Descriptor dictionary must contain FontName entry (missing in your file). From next build (202) xcpro will ignore absence of this entry, so Offsets will be filled correctly.
HTH.
Victor
Tracker Software
Project manager
Please archive any files posted to a ZIP, 7z or RAR file or they will be removed and not posted.