Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #240
| From | ken <ken@spamcop.net> |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: Bad glyph causes Adobe distill failure, but works in Preview |
| Date | 2011-06-07 07:50 +0100 |
| Message-ID | <MPG.2857da9dd92da7d2989845@usenet.plus.net> (permalink) |
| References | (2 earlier) <1ecaa8c6-b428-4e2b-aad9-b61bf5fd7ac6@j25g2000vbr.googlegroups.com> <MPG.28541143848b9d7c989841@usenet.plus.net> <ad4e9d97-66b9-4613-9891-43345de2440c@h7g2000yqa.googlegroups.com> <MPG.28568a2e3e9e72fb989842@usenet.plus.net> <ac02462d-913c-43da-a15e-dbc55132fc9e@j25g2000vbr.googlegroups.com> |
In article <ac02462d-913c-43da-a15e- dbc55132fc9e@j25g2000vbr.googlegroups.com>, jdawiseman@gmail.com says... > > glyphshow: if encoding, each glyph has to go somewhere. Given a glyph, > by what algorithm should an encoding number be chosen? Is it equivalent to a regular character, eg a capital A or whatever ? If not (its a symbol) then the exact position is irrelevant. However its still worth using an Encoding (simply use the positions incrementally from 1) rather than glyphshow, because glyphshow usually doesn't cache the glyph bitmap, so its slow. > Fonts: But if the task is left to the interpreter, and the interpreter > is Distiller, it breaks. Only if the font is broken. If the font isn't broken you catch the error, but then what are you going to do ? You still can't draw the glyph..... > The other problem is that the few thousand fonts on my Mac OS X all > seem to be of type -1, whatever that might mean. Possibly they are TrueType fonts ? How are you determining the type ? Ken
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar
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