Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Include Custom Fonts Option

  1. Advice
0
Votes
Undo
  1. Christopher Craft
    Christopher Craft
  2. PowerBuilder
  3. Tuesday, 2 July 2019 23:08 PM UTC

PB 2017 R3

We delivered our latest software on R3 and it didn't take long for a customer to report that his PDFs now show all weird characters when viewing on his iPhone.  I had them set the option in the PB.INI file and everything was fine after that but it now raises some questions. When deploying our application I had assumed that 'Custom Fonts' was a low use case but come to find out the 'Calibri' font is not found on iOS. Since this report was fine using GhostScript I am guessing either GS packages the font by default or it always translates the font to something else before it saves as PDF. I am a little hesitant to deliver this setting on because of the resulting file size but it sounds like I might have since PDF's should be viewable on any device! So my questions are:

1) Has anyone else delivered this setting on?

2) Is there something I should be aware of when using this option?

3) Is there a downside beyond the file size?

4) Is there a place I can find the Fonts that are 'Custom' (I know but I have to ask)?

5) Can NativePDF do what GS did regarding fonts (whatever that is)?

 

Thanks again,

Chris Craft

Error create http client on Citrix
Cursor is not open
Who is viewing this page
mahmoud mahmoud
Accepted Answer
mike S
mike S Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 14:37 PM UTC
  2. PowerBuilder
  3. # Permalink

1. yes, i have the include fonts option on in the pb.ini.  I hate that it requires pb.ini .  i don't care about the pdf size and have not had any comments about it.

 

 

Comment
Christopher Craft
  1. Christopher Craft
  2. Wednesday, 3 July 2019 15:28 PM UTC
Thanks Mike, good to know. And I agree, we should be able to set it using Modify.
  1. Helpful
There are no comments made yet.
Responses (4)
Christopher Craft
Christopher Craft Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 15:25 PM UTC
  2. PowerBuilder
  3. # 1

Chris,

Using the conformance worked but when I use 1a or 3a then when you search for text (or try and select text) it highlights more than what I was searching for. All the other conformance options will only highlight what I typed.

So, since the conformance setting embeds the font I am guessing the IncludeCustomFonts setting does the same thing minus the conformance standards. That sounds like the best option because it gives the user control to set the conformance for specific reports if need be.

Thoughts?

Thanks again,

Chris Craft

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 3 July 2019 17:37 PM UTC
Hi Chris;

The "conformance" may still need to be "tweaked" or a new Apple type added (just a guess). I would like to suggest that you open a Support Ticket ( https://www.appeon.com/standardsupport ) on this issue so that Appeon can delve deeper into this iOS PDF issue.

Regards ... Chris
  1. Helpful
Christopher Craft
  1. Christopher Craft
  2. Wednesday, 3 July 2019 18:10 PM UTC
I think the only thing that might need to be tweaked is it should always embed the font regardless of the conformance setting (Which is what GhostScript does). To have the default be where the PDF relies upon the fonts installed on an OS seems odd. To me the ini setting should be an override to NOT include the font - and better yet, that option should be in the DW. Maybe you can ask engineering to chime in with the reason it was defaulted this way?
  1. Helpful
There are no comments made yet.
Christopher Craft
Christopher Craft Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 13:39 PM UTC
  2. PowerBuilder
  3. # 2

Thank Chris - I will give that a try.

Chris Craft

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 July 2019 00:36 AM UTC
  2. PowerBuilder
  3. # 3

Hi Chris;

  This would be the case if the PDF was rendered using a "PDF Conformance" that iOS cannot handle. If I remember correctly when I tested this way back in PB2017Rx days ... try "PDF /A - 1A" - I think that worked for me.

HTH

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.