Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Kent Lew

About

Username
Kent Lew
Joined
Visits
1,845
Last Active
Roles
Member, Type Person
Points
531
Invited by
Admin James Puckett
Posts
506

Comments

  • Rob'in — That is basically another of the potential practical uses I can imagine. But, as you say, that’s reading into things a bit. To expand upon this a little: to be really practical for tabular use, in my opinion, such a space would be f…
  • Khaled — I saw that. But I’m not inclined to take this at face value. For one thing, the 1837 example cited is not really an example of a specific “punctuation” space. That’s kinda just how English was typeset back then — with various spaced punctua…
  • Paul — Thanks for your observations. Yes, banknotes are almost never any use for gauging native use of a currency symbol, as most do not display one.
  • Not looking for a new structure, thanks. I’m interested in what the folks who use this currency find familiar and expect of their symbol.
  • ÐðÞþ — Thorn and eth: how to get them right ĄąĘę — Polish Diacritics: how to?
  • Grolier Club (grolierclub.org). Looks like there will be a calligraphy exhibition, curated by Jerry Kelly, when you’re going to be there. (Not typography per se, of course, but probably of interest.)
  • The question becomes, should a width axis then be considered "non-literal"? In the sense you’re talking about: Yes. This is probably not intuitive in terms of user expectation, Really? Are there users who expect to change the weight of a font an…
  • Addendum: Actually, looking more carefully, I see now that there are a couple faces with these additional sorts in the 1948 Supplement — mostly popular book faces: Caledonia, Electra, Janson, et al. I guess TNR was too new to the library for these …
  • Nice to see confirmed. I had checked my Linotype Supplement from 1948 and they don’t appear there. It would be interesting to know what prompted Linotype to make up these punctuation logotypes for Times and when they were introduced. This was not a…
  • A couple things to try: • Eliminate the space after the "s.beg_commaaccent" and before the bracket. The white space shouldn’t matter, but you never know. • Similarly, you could try deleting the line return at the end of that line and reinserting i…
  • How was your kerning developed and defined? That error (the second part) looks like there is class kerning in an explicit {kern} feature that references a kerning class that is undefined.
  • Also, it may still be common to find Chuvash using Latin ă ĕ (and ç) chars in place of properly encoded Cyrillic forms, perhaps due to legacy habits. I would expect that, in any example where one finds mismatched breve forms intermixed, the differen…
  • Yes, it can be found. But most such examples tend not to be community-based use. That’s all. I’m not arguing that it should not be included in a font. Just adding a qualifier on the notion of “language support.” And I, too, do not design it as a co…
  • I’m not saying it shouldn’t be included in a font that claims support, but . . . I am told that the ₫ symbol is rarely, if ever, actually used in Vietnamese communities. It’s hard to find an example in the wild. More often a simple đ or Đ abbreviati…
  • Didn’t the representation of our modern concept of zero as numeral/figure basically start out as a contrastless symbol from the beginning? I would think the relevant question is when in history did contrast get added to harmonize it with the rest …
  • Yes, I would not expect FontLab 5 to be able to compile this feature code. You will need to use a different application to compile your fonts, or post-process with FontTools or OTM or something like that.
  • Also, if you look at the source files for Adobe Source Sans Pro, in the family.fea file you can see this in practice. Which is where I basically cribbed together this example for you from: feature ss01 { # Stylistic Set 1 featureNames { …
  • Most large publishers have a specific department to deal with copyrights and permissions. Don’t know what kind of response you’ll get about an older book like this, but it seems like the place to start. Looks like this is now handled by the curren…
  • Ramiro — The relevant attribute via Robofab is f.info.openTypeOS2Selection = [7] But I don’t think this is supported in FontLab .vfbs.
  • Seems to me the whole reason this is an issue is because the small-cap mechanism in the OpenType Layout framework was conceived to operate outside of any text-level casing mechanisms, and so the type designer or font engineer is left with the task o…
  • You’re talking about a library of analyzers that can identify various common glyph parts and report the associated points, right? I think Petr van Blokland has done some significant work along these lines in the context of development of various …
  • Plenty of respectable fonts from large families don’t have IDs 16 & 17 for RIBBI styles. Like Minion Pro and Myriad Pro, for instance. Or Georgia Pro and Verdana Pro.
  • Or, put another way, IDs 16 & 17 are only typically needed for those beyond the core RIBBI styles.
  • That enumeration is not a canonical ordering; that is just a list of different numbered lookup types. If you crack a compiled font into FontLab, then generally it will list the {kern} feature first in its OpenType panel, since the GPOS table is com…
  • I’m not aware of any canonical order for OTL features in the OT spec. There are some common practices and rules of thumb, and certainly consequences, but not a technical specification that I’m aware of. In terms of actual feature order. As Erwin sa…