Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Defining Custom Fonts | ||||||||
Line: 74 to 74 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 90 to 90 | ||||||||
The font will be embedded in the PDF document so the custom font should be viewable and printable on all systems whether the font is installed on the system or not.
PDF Debug Logging | ||||||||
Changed: | ||||||||
< < | If you are having trouble getting a custom font to print you can gather debugging information by setting the following environmment variable prior to starting an APPX session: | |||||||
> > | If you are having trouble getting a custom font to print you can gather debugging information by setting the following environment variable prior to starting an APPX session: | |||||||
set PDFLIBLOGGING=filename=c:\pdf.log enable remove classes={filesearch=9 api=2 resource=9}
"enable" means that you want to enable logging "remove" means that you want PDFlib to remove any log file (of the same name) before starting The "classes" clause specifies the information you want to log (and the level of detail for each category) | ||||||||
Changed: | ||||||||
< < | It would be helpful to include the log generated by this processs when reporting PDF output issues. | |||||||
> > | It would be helpful to include the log generated by this process when reporting PDF output issues. | |||||||
-- GaryRogers - 2010-06-01 |