Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #3271
| Newsgroups | comp.lang.postscript |
|---|---|
| Date | 2018-06-18 14:22 -0700 |
| References | <c66ccb1f-ee64-48c2-9d80-0c018c89b137@googlegroups.com> |
| Message-ID | <80d271e1-9d5c-489d-853b-11225edbbf74@googlegroups.com> (permalink) |
| Subject | Re: Interrogating a font |
| From | deedubman@gmail.com |
Doesn't ascender refer to lower-case letters that project above the x-height like b, d, f, h, k, l, and t? I would take the max of this set. Also take the min of g, j, p, q, and y for descender. For stem-v I remember doing a small survey of fonts for which I had AFM files (which have stem-v) and then trying to tune an algorithm such as you described to match the known data, maybe make a wide but thin clip rectangle that crosses the stem of "I" in the middle, which is also 'true charpath clip', then 'clippath pathbbox' that result, get the width. If it could reasonably guess at known stem-v values then I could trust it in the unknown case. But then I noticed (if we are talking about PDF) that a lot of PDF software seems to not care about the stem-v value in font desccriptors, it was often zero. David
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar
Interrogating a font luser droog <luser.droog@gmail.com> - 2018-03-27 15:57 -0700
Re: Interrogating a font Mark Carroll <mtbc@bcs.org> - 2018-03-28 07:32 +0100
Re: Interrogating a font deedubman@gmail.com - 2018-06-18 14:22 -0700
Re: Interrogating a font luser droog <luser.droog@gmail.com> - 2018-06-18 23:13 -0700
csiph-web