Howdy, Stranger!

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



Last Active
Member, Type Person
Invited by
Admin James Puckett
  • Re: Naming the Widest Width

    How about Widey McWideface?
  • Re: Low vision calendar company seeks a better font

    Agree with Aaron, IKEA wouldn't have picked it for huge posters if it didn't work at large sizes. ;-)
  • Re: Duospace. Wait, what? Duospace?

    From experience having non-monospaced characters in a font that declares itself as monospaced can cause problems in some apps. 
  • Re: Foundries Allowing Modification

    My take: Initially early digital foundries simply followed Adobe's model, where modification was explicitly allowed in their FAQs (even if their EULAs were more ambiguous).

    Adobe took this approach because they just didn't want to have to deal with the hassle of one-off modifications and licensing requests - they could leave this in the hands of customers - "modify the font as you see fit but make sure whoever you give it to has a license to the original". 

    I think most type designers today want to be involved in modification - either doing that work or approving of the work - this extends to open source fonts too - the OFL restrictions around font names being evidence of this. 
  • Re: Plex; IBM's new font identity model

    I wonder if promoting the font as open source is misleading. Why not say the font is free to use and modify under the SIL, and that the intent is to open source it within the next 13 months? Alternately set a lower bar for the sources, and publish the Glyphs sources.