LyzaTechops:
We have pdf.SetUnicode() in our code. But as I indicated usage of the setIsFontEmbedded with a value of true is what is causing the issue. If I remove the line won't our generated PDF's no longer contain the embedded fonts? That means that if the user does not have the font specified installed the document will no longer look the same. Correct?
Hi Steve,
Sorry for delay in response over this query.
I would like to share some more comments along with Nausherwan's statement. Please note that when calling SetUnicode(....) method, only the subset of TrueType fonts used in PDF document are included in PDF file. Whereas when calling setIsFontEmbedded(....) method, the TrueType fonts being used during PDF generation become the part of PDF file so the size of PDF file generated in this approach is greater as compare to the one generated when using SetUnicode(....) method.
If we do not call any of these methods, when viewing the PDF file on a system which does not have these fonts installed, the contents of PDF file will be displayed in default font. In case you have any further query, please feel free to contact.
LyzaTechops:
Is this scheduled to be addressed? If so when?
Hi Steve,
Thanks for your patience.
Our development team is working hard to get this issue resolved and we already have made significant progress towards its resolution. Nevertheless I have requested them to share the ETA regarding its resolution. Soon you will be updated with the required information. Please be patient and spare us little time. We are sorry for your inconvenience.
The problem is not unique to Java; we are using the .NET version of Aspose PDF and in testing v7, I also noticed this problem.
Hi Mark,
Thanks for using our products.
Can you please share some details regarding sample source code and template documents you are using or create a sample application to show the issue. This will help us to figure out the exact issue and reply back to you soon.
We apologize for your inconvenience.
Thanks & Regards,
Hi Rashid,
I have sent you email with a test solution attached.
thanks
Mark
Hi Mark,
Thanks for sharing the details.
We are working over this query and will get back to you soon. Sorry for the inconvenience.
Thanks & Regards,
Hi Mark,
Thanks for your patience.
I tested the scenario using your provided source code and unable to find any issue. However, during my testing I also changed font from "Frutiger LT 65 Bold" to "Courier New" and it applied successfully. Resultant PDF documents are attached for your reference.
Please feel free to contact support in case you need any further assistance.
Thanks & Regards,
Hi Rashid,
If I compile our code against 6.6 the font appears as intended. However, if I compile with either 6.7, 6.8, 6.9 or 7.0, the reported problem appears.
Clearly, something changed with 6.7 and I would argue that if the document is rendered with a font other than what the code specifies, then it must be a bug, and quite a glaring one. Having said that, you have seen how we are setting and using fonts, so if we are doing something wrong, I would like to know what it is.
Please either identify and correct the bug, or help illustrate what we are doing wrong that is causing the issue, so we can rectify it at our end.
There is no other satisfactory option, because there will inevitably be a time where we need to upgrade beyond 6.6 (perhaps even now to correct PDFNEWNET-33459) and we need assurance that pathway will be available to us.
Thank you
Mark
Hi Mark,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
We are very sorry for the inconvenience and delay in the response.
Actually, Rashid has left our team and I would request you to please send
the test solution again so we can further proceed with the testing of this
issue. Again, I am very sorry for the inconvenience it might cause you.
Thank you for your understanding and support,
Thanks Nausherwan, I created a new thread to group a few of our issues, and the details and code sample is now there.