Prinergy Troubleshooting - Normalizer fails with undefined error and offending command message

Normalizer fails with undefined error and offending command message


Product		Prinergy (all)
Platform
Operating system

Error		Error: undefined; OffendingCommand: <square> <square>" (2 non-printing characters). Diagview displays "Error: undefined; OffendingCommand: [0005][0016]" or similar message.

Symptoms		Normalizer fails on a certain file and reports "Error: undefined; OffendingCommand: <square> <square>" (2 non-printing characters). Diagview displays "Error: undefined; OffendingCommand: [0005][0016]" or similar message.

Cause		There is 128 bytes of unexpected data at the beginning of the PDF file, prior to the "%PDF-1.4" comment. This extra data might be the Mac's data and resource forks getting combined. Normalizer is failing on some of the binary characters in that header. It is not clear what introduces this extra header information into the file. Possible causes may be network transfer through an old protocol, like MacBinaryIII, or transmission through an improperly-configured FTP client.

Solution		There are three possible solutions to this problem: 1. Export PostScript from Acrobat. 2. Run the PDF file through Stuffit Expander. This strips out the extra header information on the file and Stuffit will give you a new file named after the page name. 3. Try re-saving the PDF from Acrobat. Permanent fix:

See also

Keywords		PDF, file formats, normalizer

Technical contact(s)		James Bredenhof
Submitted by		James Bredenhof
Date submitted		30 Mar 2005