If you try to use Cyrillic or Japanese characters on PDF banner pages with a workflow
that uses the default values for the Header page configuration file and Trailer page configuration file properties, the characters do not display correctly.
If AFP support is installed and your job was sent to an AFP printer, where it printed
on the wrong paper (for example green instead of blue paper), you might need to update
some job or printer properties.
If your job was sent to a Ricoh PDF, Custom PDF, or Ricoh TotalFlow printer and it
printed on the wrong paper (for example green instead of blue paper), you might need
to update some job or printer properties.
When a job stops in the No matching device state, check the Requested printer property and make sure that the scheduling properties for the job match the corresponding
properties of the requested printer.
When a job stops and the value of the Current job state details column is No matching media, the media name or media properties in the JDF job ticket or overrides file for the
job cannot be matched to an existing media object.
If you see an out of memory message or encounter slow processing when printing a large
PDF file, you can set the Merge banner pages into PDF print file property to No or increase the Java Virtual Machine (JVM) memory. Merging banner pages on large
PDF files takes more memory and system resources than printing banner pages as separate
files. If you need to merge banner pages, increase the JVM memory.
If you have trouble with document property values that are extracted from PDF files
using Ricoh ProcessDirector Plug-in for Adobe Acrobat, the fonts included in the PDF file might be incomplete or contain different UNICODE
mappings than you expect.