Re: Bad glyph causes Adobe distill failure, but works in Preview

From	ken <ken@spamcop.net>
Newsgroups	comp.lang.postscript
Subject	Re: Bad glyph causes Adobe distill failure, but works in Preview
Date	2011-06-04 10:54 +0100
Message-ID	<MPG.28541143848b9d7c989841@usenet.plus.net> (permalink)
References	<989b39ed-2a02-4b74-b4ce-e07ec9d70920@z13g2000yqg.googlegroups.com> <MPG.2852ffede6b4aaed989840@usenet.plus.net> <1ecaa8c6-b428-4e2b-aad9-b61bf5fd7ac6@j25g2000vbr.googlegroups.com>

Show all headers | View raw

In article <1ecaa8c6-b428-4e2b-aad9-b61bf5fd7ac6
@j25g2000vbr.googlegroups.com>, jdawiseman@gmail.com says...

> But, as you say, Adobe Distiller isn?t conforming. (And Adobe doesn?t
> say to what extent this has been fixed in Acrobat X Pro ? one lost
> sale.) So, is there a way in PostScript to have a chance of trapping
> this error?

In PostScript, yes, using Distiller, no.

 
> For instance, perhaps ?currentfont /CharStrings get GlyphToTest get?
> has testable properties, some values of which must be bad?

If all you want is to know if a glyph exists in a (PostScript) font then

currentfont /CharStrings get /name known will return true if /name is a 
named entry in the CharStrings dicitonary, and false if it isn't.

Note that this will *not* work for CIDFonts, type 0 (OCF) fonts or Type 
42 fonts. You would need to do other kinds of tests on these fonts.

Using glyphshow is bad practice, its slow and can make PDF files which 
are unsearchable. You should define an Encoding array which uses the 
glyphs you need instead. Obviously its quite reasonable to test for the 
exsitence of those glyphs first :-)



			ken

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-03 01:46 -0700
  Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-03 01:46 -0700
  Re: Bad glyph causes Adobe distill failure, but works in Preview ken <ken@spamcop.net> - 2011-06-03 15:28 +0100
    Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-03 11:45 -0700
      Re: Bad glyph causes Adobe distill failure, but works in Preview ken <ken@spamcop.net> - 2011-06-04 10:54 +0100
        Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-05 04:15 -0700
          Re: Bad glyph causes Adobe distill failure, but works in Preview ken <ken@spamcop.net> - 2011-06-06 07:55 +0100
            Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-06 14:49 -0700
              Re: Bad glyph causes Adobe distill failure, but works in Preview ken <ken@spamcop.net> - 2011-06-07 07:50 +0100
                Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-07 02:00 -0700
                Re: Bad glyph causes Adobe distill failure, but works in Preview ken <ken@spamcop.net> - 2011-06-07 10:37 +0100
                Re: Bad glyph causes Adobe distill failure, but works in Preview jdaw1 <jdawiseman@gmail.com> - 2011-06-07 16:56 -0700

csiph-web