Howdy, Stranger!

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

Katy Mawhood


Katy Mawhood
Last Active
  • Re: Font or Font Software

    Can you provide links? It sounds really strange to mix information and artwork in one term...
    Sure, here's two examples from earlier:

    1) Commercial type
    For the purposes of this Agreement, “Font Software” shall be defined as the design of the Fonts together with the Font Software which, when used generates the typeface, typographic designs and, if applicable, ornaments or other designs. 

    2) Type Together
    License to use the Font Software (“Font[s]”) and the designs embodied therein together with any accompanying documentation

  • Is it ok to call a "typeface design" the UI of a font software program?

    Opinions welcomed.

    I'm always looking to communicate font software / encoding to non-type people. The objective is to differentiate "font software" from an "image of lettering", clearly and quickly with minimal jargon. The term "User Interface" (UI) enables a quick analogy to the visual setting underlying software in a phone or an app, which most people are familiar with. But, is it fair to describe the typeface design as the UI of the font software?

    I initially got the idea from reading this passage:

    ‘a book can be considered a user interface to its content… a technical research paper can be seen as a user interface, that to succeed must take account of its intended user community…almost anything can be seen as a user interface; doing so will highlight certain issues of design and representation that might otherwise remain obscure,’ – GOGUEN, J., ‘An Introduction to Algebraic Semiotics, with Applications to User Interface Design’, in Computation for metaphors, analogy and agents, ed. by C.L. Nehaniv, LNAI, 1562 (Berlin: Springer, 1999), pp. 242–91
  • Re: Licensing Unit: Devices vs Users

    To follow from @Johannes Neumeier's excellent point, what is a CPU today? Our font management software is setup to measure license count by user. To add any device that could be deemed as a CPU would be a significant headache.

    EULA definitions affect things, particularly when well-considered. CPU licensing makes sense for some businesses.

    If a EULA gives a licensee one option, it will likely be interpreted according to their "best-case" scenario (e.g. CPU, Workstation, Device, User… some other thing). It's amazing how many assumptions are made, quite a minefield. Identifying the specific details with licensors is often no less befuddling, time-consuming and riddled with uncertainty on both sides.

    E.g. It's nice to chat about the details, but it doesn't always reflect the reality. In the case of legal dispute, lawyers will argue both sides – not the "right" side.

  • Re: Best Foundry Sites

    Thinking out loud... I'd be interested whether trial licensing influences the use of online testing features.
  • Re: Public domain pros and cons

    This is off-topic, but it's quite entertaining:
    Several companies have parodied this belief that users do not read the end-user-license agreements by adding unusual clauses, knowing that few users will ever read them. As an April Fool's Day joke, Gamestation added a clause stating that users who placed an order on April 1, 2010 agreed to irrevocably give their soul to the company, which 7,500 users agreed to. Although there was a checkbox to exempt out of the "immortal soul" clause, few users checked it and thus Gamestation concluded that 88% of their users did not read the agreement.

    Grappling with the license / contract terminology:
    IP licensing form[s] sub-branches of law born out of the interplay of general laws of contract and specific principles and statutory laws relating to these respective assets.