Hi Robert, Usually this problem is caused by the default mapping between the fonts used by FOP and the fonts installed in the operating system. The default fonts used by FOP do not contain the characters that are displayed as '#' in the PDF output, so you will have to find one or more fonts that are able to display these characters and you will have to set them in the Docbook PDF transformation. First you should find a font installed on that system that is able to display the characters that were replaced with '#' in the PDF output. You should look in the list of fonts available to the Java Virtual Machine in order to see the font names available to Oxygen as Java application, because you will have to use such a font name in the Docbook PDF transformation. Please go to menu Edit -> Insert from Character Map and look for a font that contains the characters that we need (the characters that are displayed as '#' in the PDF output). When you find a font you have to set the font family name in the parameter called body.font.family of the Docbook PDF transformation. You need a font name also in the title.font.family parameter. If you want a different font for the titles in the PDF output (chapter titles, section titles, example titles, etc) please find a second font that can display all the characters in the titles of your PDF output and set it in the title.font.family parameter. Otherwise you can set the same font family name in both body.font.family and title.font.family. The above procedure helps you to find a font with all the needed characters in the list of fonts already installed in the operating system. If you can't find a font with this procedure you will have to find and configure an external font for the FOP processor. The procedure for that is: http://www.oxygenxml.com/doc/ug-editor/index.html#tasks/add-font-to-builtin-... Best regards, Sorin http://www.oxygenxml.com Robert Nagle wrote:

HI, there,

I am helping a client use Oxygen to produce a PDF of my Docbook 5 project. (In case you are wondering, this is NOT the same client I asked about last week --- but a different one from two years ago!)

The docbook 5 project is valid. When I run the out-of-the-box Docbook 5 PDF (with FOP), I can generate the project on my machine. But my client generates a file successfully (with no errors or messages) with the latest XML Editor -- except it's nothing but # characters.... I seem to remember having encountered the same error before, but I don't remember what I did with it.

Both of us have Win 7 64 bit versions. I Have Author 16 while my client has Editor 16 which was just installed today. We have made no customizations yet to the transformation.

I'm guessing it's an encoding error, but I'm not sure where to go fix it (or why a clean Editor install with a general Docbook 5-fop-pdf would give that kind of message). Do you have any ideas?

On another note, I want to thank* *Sorin for helping me with my problem last week.

Robert