Backquote problem composing to PostScript

Submitted by: Peter Karman Last Updated: 2006-06-18

=Problem=

Migrating to Epic 5.1 from 4.2. I have started seeing this error when composing to postscript:

No character set is defined for entity "&backquote"

I don't get that error using the same FOSI under 4.2.

=Solution=


 * making a copy of the default charent.cf file in Epic-path/lib and putting it in my custompath/lib directory
 * editing it to change this line:

backquote     -               -       unicode 96            # ` to this:

backquote      ascii           96      unicode 96            # `

Note sure why backquote was not defined to use the regular ascii char 96, but this was causing Bad Things for common use of that char (whether as an entity or hardcoded).