Howdy, Stranger!

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

James Puckett


James Puckett
Last Active
Member, Type Person
Invited by
Admin James Puckett
  • Re: discuss with me my latest work.

    This typeface suffers from mixed metaphors; being both a new take on serifs and Cheltenham. The ball terminals are one font. The squarish round glyphs come from another. The traditionally terminaled v w x z from a third. k is a mongrel offspring of h and v, y is the sci-fi child of three worlds. Upper serifs are some new semi-flaccid metaphor, baseline serifs are mired in the time of Clarendon. It’s like those special episodes of Dr. Who where six time lords are all running around like maniacs and the Tardis is on the edge of imploding.

    Reconciling all of these in a single font isn’t going to happen. Pick a direction—something new, or something Goodhue—and run with it. I recommend the new angle; I don’t think Cheltenham is making a comeback any time soon. But what do I know; I thought Brandon Grotesque would be the last word on the low x-height geometric sans fad.
  • Re: Enabling HTTPS

    And also I think there are open source free options available to create a forum like TD.
    Open source is only free if the responsible parties’ time is worth nothing. Expecting James to port over all the data and start managing the forum software is a bit much.
  • Re: SepidKhan: An alternate for Persian/Arabic braille

    Wow. This is impressive work. A great reminder that while Latin Type designers keep the infill coming, people working with non-Latin scripts are doing work of serious importance.
  • Re: Efficiency in kerning pairs

    There’s a continuum of desire to add kern pairs. On one end are fastidious type designers who try to kern every possible thing that goes wrong; they can’t bear the thought of opening a magazine and seeing gaps in W,” set with their types. The users and readers must be protected. These users have thousands of kerns in their fonts, including the numerous exceptions that come from adding the diacritical marks needed for central Europe and Vietnam.

    On the other end are the realists. They know that most designers aren’t even aware that fonts have kerning. They have accepted that many designers use optical kerning by default and think kerning doesn’t exist in browsers. They don’t bother with kerning exceptions for accents because people in those countries don’t buy fonts anyway.
  • Re: automatic spacing correction for locl FRA. Good or bad?

    This would make switching between your fonts and other fonts more trouble than it’s worth. Nobody reads the readme.txt file, so users wouldn’t know what’s going on. Especially not the users who didn’t buy or spec the fonts in a document they open years after it was created.

    And it only takes seconds to change /guillemetright /space to /guillemetright /thinspace with find and replace. So you wouldn’t be doing the user a big favor.