Oxygen XML Forum

I am trying to imply custom font to PDF. When tried adding the fonts and on generating the pdf, I get #### displayed instead of text content.

Could you please let me know about how to get the custom font displayed in the pdf.

- Sekar

Hi,

Are you using a common format of XML document (DITA, DocBook, etc) that you transform to PDF or do you have a custom XML format?
On what platform (Windows, Linux, OS X) are you running Oxygen?

Depending on the FO Processor being used, you may have to configure it to handle your custom font. See here details on how this is done for the Apache FOP included with Oxygen:
Add a Font to the Built-in FOP - The Simple Version
If the font is not installed on your system, you'll have to do this the hard way:
Add a Font to the Built-in FOP

Regards,
Adrian

I am using Docbook5 format on Windows 8 64 bit platform. The custom font is installed in my system and i can access them in word document.

But I could not able to generate a pdf from xml document with that custom font. Could you please guide me through.

- Sekar

I would need to generate a PDF from DocbookXML. I use Apache FOP to get the PDF, it is the same which is used by Oxygen XML editor.

We followed the same instruction as mentioned in the links you provided. But just getting '####' displayed instead of characters. The same happens if I try removing the custom font. So, it doesn't seem to accept the font that I've included.

Could you please advice me on this. Thanks.

Regards,
Sekar

Hi,

Have you checked if the font in question supports the characters involved (the ones that appear as #### in the PDF output)? Test in Word (or Wordpad) by pasting those characters there and setting that font for them.

To see what happens when processing the PDF, enable Apache FOP output (verbosity). Go to Options > Preferences, XML > XSLT-FO-XQuery > FO Processors and Enable output of the built-in FOP.
Run the transformation again and you should see the entire log output of Apache FOP in the results panel. Send us that output log to support@oxygenxml.com and also a small sample file that contains the problematic characters.

Regards,
Adrian