Font naming - Foundry prefixes

Comments

• Chris Lozos Posts: 1,457

  May 2018

  I think it helps find the font.  I am more likely to remember the foundry name than the font name.  It also helps with copyright.

  0
• Nick Shinn Posts: 2,059

  May 2018 edited May 2018

  It’s always seemed to me that prefixing a typeface name suggests there are versions by other foundries, alternatives which might be considered. That’s a mindset I’d like to avoid, for various reasons. 
  
  However, if one is publishing versions of the classics (Bodoni, Garamond, etc.)—which both ITC and Adobe, that you mentioned, have done—it may make sense.

  4
• André G. Isaak Posts: 622

  May 2018

  I much prefer foundry suffixes to foundry prefixes since the latter affects sorting.

  3
• Erin McLaughlin Posts: 45

  May 2018

  @André G. Isaak can you elaborate on sorting?   you just really want all designs in alphabetical order of the font name?
  
  I have heard advice from many people to name your fonts "toward the beginning of the alphabet" for the reason I think you're implying. I have very often forgotten the names of fonts I'm looking for and have played the font menu scroll/preview game many times. But I wonder if the visual "hiccup" in the list of fonts, created by a block of prefixed names, would act as a sort of bookmark/point-of-interest for someone scrolling through their library? Might be a good thing??

  1
• Jess McCarty Posts: 97

  May 2018 edited May 2018

  Minority opinion, I'm sure. But the prefix sorting can be a bonus, as all of your fonts will appear together within app font menus. (If you're wanting to loop in beginners.)

  2
• Thomas Phinney Posts: 2,585

  May 2018 edited May 2018

  I think it is desirable to the foundry to have their fonts group together and have the foundry name included. Less value from the user perspective, especially for a prefix... if one assumes that users remember font names more than foundry names.
  
  As a user, I dislike foundry prefixes (except for "generic" typeface names like Bodoni, Garamond, etcetera, but even then I prefer a suffix). The prefix means that unless I remember the foundry, I don't know where to look in the menu.
  
  I do not mind a foundry suffix, but I don't really find it much of an advantage either. But then again, I use font management, so I have ways of searching by foundry, etc. The average user does not have a font management app these days, I don’t think.

  6
• JoyceKetterer Posts: 769

  May 2018 edited May 2018

  I've always understood the primary reason for foundry prefixes (or suffixes) to be getting around the problem of finding available words for font names.  We don't like it because gets in the way of the poetry of the name and have always seen not using them as a luxury we may some day need to live without.  Perhaps I'm being simplistic?

  3
• Andreas Stötzner Posts: 750

  May 2018

  As a font man I prefer short or strange font names. As a user I believe in short font menus.
  

  0
• Thomas Phinney Posts: 2,585

  May 2018 edited May 2018

  Joyce: I am not sure if what I am reading you as saying is what you meant, so forgive me if this is a misinterpretation.
  
  If a font name is trademarked by somebody else, putting your foundry prefix in front of the trademarked name does not normally get you off the hook for trademark infringement. If I trademark a font named “Pretense” and Very Good Looking Fonts tries to release “VGL Pretense” my lawyer and I would be sending them a polite but firm cease-and-desist note.
  

  6
• JoyceKetterer Posts: 769

  May 2018 edited May 2018

  @Thomas Phinney We all know that naming is the episiotomy of font design (would legitimately be torture under other circumstances but in context is just one more indignity).  So you're right about the scenario you describe and you're also right that I wasn't being clear.  I'm guilty of short handing.  
  
  Here's the context I was thinking of:   One of the many concerns in font naming is abandoned marks.  For instance, as once happened to us with a trademark search, someone in the 90s might have made a free font packaged in with thousands of others under the name you want to use.  That someone went out of business ages ago and they aren't maintaining the font (any court would say they've abandoned it) but it can still be found online.   The fact that 90s font can still be installed on computers is a problem because it can mess with installations and caching and so on. 
  
  We found another name.  But my understanding is that one of the reasons for the suffix is to make it possible to just keep your name in this situation where it is legitimately available but there are technical concerns.    

  4
• André G. Isaak Posts: 622

  May 2018

  Can you elaborate on sorting?   you just really want all designs in alphabetical order of the font name?
  

  For installed fonts in font menus, yes. I’m more likely to recall the family name then I am to remember which families have a prefix vs. a suffix vs. no vendor code at all.
  

  6
• Johannes Neumeier Posts: 340

  May 2018

  This thread seem to be dominated by mostly reasonable yays, yet here's an emotional nay: To me it feels cheap. Is the font not good enough to stand on it's own name? Is the foundry more important than the type? Why would I even care what foundry made the font once I've bought it?
  

  2
• AbrahamLee Posts: 262

  May 2018

  As I’ve read through all these responses, it’s made me think about why I do. So, here’s a philosophical question for you: Why does any company put their name next to their product’s name? While a consumer will usually know which company the thing came from, I think we can all agree that a company’s reputation, for better or worse, changes the way we think of that product. There’s always the quality level associated with the company that it hints at. I’m not saying a font name can’t stand on its own, I’m saying that maybe a foundry may want their fonts to be remembered a certain way, possibly from a quality standpoint, maybe from the unique approach they always take, maybe for the extensive character set, maybe because they always awesome specimens, maybe from their customer service. I guess what I’m saying is there are lots of reasons, including just so people know better who made it in hopes others will find them easier and they can get more sales. Or maybe it’s nothing more than the foundry struggles to be creative with their names. I know I’ve been there.
  
  My 2 cents.

  3
• Roel Nieskens Posts: 178

  May 2018

  When it did come up, front-end/web developer peers just accepted it as part of the font name. I don't think most developers realise this is some kind of indication about the foundry.
  
  I must admit I realised it myself only when I was pretty far into "font territory".

  3
• Erin McLaughlin Posts: 45

  May 2018 edited May 2018

  Thanks everyone for all of the comments so far!!
  
  I like what you said, @Roel Nieskens - in my early computer years, I totally do remember assuming that ITC meant something technical about the font (like a Pro suffix) before I knew that it was the name of a foundry. This sort of "newcomer" perspective is totally what I'm interested in hearing. Thank you!
  
  I was definitely expecting a lot of negative reactions toward it, from the classy type designer perspective, along the lines of what @Johannes Neumeier just said. 
  
  I really do like the comment by @AbrahamLee, about it seeming like a mark of quality (if that's the case), and a branding feedback loop, like what @Jess McCarty said.
  
  To @JoyceKetterer's point, if unique names for fonts are getting harder and harder to find, I wonder if prefixes/suffixes are inevitable? I was just scrolling MyFont's best sellers list, and I see "Averta", which I thought said "Alverata"... to me it's just so confusing. I am struggling to figure out why a foundry wouldn't try to further brand their font? It's like a free logo stamped onto your product!?
  
  So are we thinking that companies aren't doing this because type designers are naturally averse to aggressively marketing their products? That most of us aren't comfortable with that side of the business??
  
  FWIW, I just took a tally, on the MyFonts best sellers page, 30/50 of the fonts have a ™, ®, or a foundry prefix. I definitely think that foundry name/prestige, and the appearance of being an authority on typography, must have a big impact. Yes yes, I know it's because everyone wants Helvetica and DIN because they are "standards", but I really think there's a correlation there...
  
  Any thoughts?
  
  * edit:  and on the "Hot new fonts", 12/50 had ™, ®, or a foundry prefix. 5 had "Pro".  So... 1 in 4 fonts had some sort of visual cue like this...  
  

  3
• Dan Reynolds Posts: 164

  May 2018 edited May 2018

  As I wrote on Twitter, I see the addition of trademark or registered trademark symbols onto the end of a font’s display name on a website (or when it is discussed in print) as belonging to a different category than what you started this thread asking about: foundry prefixes in font names.
  
  I think that you are correct when, as you wrote on Twitter (generally my favorite place for type discussion, rather than here, sorry!), many fonts look the same, and the best way to differentiate them
  from one another is (and will be) marketing. But please don’t reduce marketing to putting foundry prefixes in front of names. You will differentiate FontWala through a number of things, I suspect: your website, they way you personally interact with customers and potential customers, the quality of your fonts’ design (you are probably one of the best graduates the MATD course ever had), your copywriting about the fonts on your website and maybe elsewhere, like on other design websites or in design magazines, etc. And so on.
  
  There are hundreds, of not thousands, of small “foundries.” If even 5–10% of them had foundry prefixes, the world’s font menus would be a total mess! To be honest, I think that what Adobe, FontFont, ITC, Linotype, etc. wrought on the font world in this respect decades ago was too much. Their prefixes are anti-user, and branding of the wrong kind (at least for today). Don’t do it! There are better ways to bind customers to you and establish your products’ names in the marketplace. I’m looking forward to seeing what it’ll be.

  9
• Erin McLaughlin Posts: 45

  May 2018

  LOL ok, not the reply I was expecting! You did warn me! Thank you, Dan!
  
  Luckily I will have lots of Indian-language words to draw from for my future releases... but what do people see as a long-term solution for the "running out of names" problem for Latin fonts, if not foundry prefixes/suffixes? More invented words? More foreign words? Numbers? Multi-word names?  "Low-Sodium Balsamic Vinaigrette Sans"?
  
  And, yes I did shift subject matter slightly, but the whole  ™ ® symbol thing... to me is  some visual indicator of  "we have money for a lawyer, don't steal this font" or "we have money, therefore we make high-quality stuff" or something...  what do people think this might indicate to consumers? I'm just curious.

  1
• Ray Larabie Posts: 1,337

  May 2018

  Someone tried to convince me to add a prefix/suffix to my typeface names a long time ago but I didn't like the look of it. It seemed to compromise the clean look of the name like The Mission UK, Bush-X, Charlatans UK, The English Beat, U.K. Squeeze etc.

  1
• Benedikt Bramböck Posts: 37

  May 2018

  At least with FontFont® (sic!) it is (or maybe was?) also important to consider that something like FF Legato is a “marketing name”, while the actual font will be called Legato and appear under L in applications.

  4
• André G. Isaak Posts: 622

  May 2018

  People have already mentioned the desirability of a foundry designation in cases like Bodoni, Garamond, and other families which have been subjects of multiple revivals.
  
  To this, though, I would add that I prefer it when a vendor designation is added to fonts which have been digitized and/or cross-licensed by numerous different foundries and/or vendors. A good example would be Helvetica, which Apple, in it’s infinite wisdom, has included as a *required* system font. This would have been fine if they had called it ‘Helvetica OS X’ or something along those lines, but as it stands it’s a royal PITA if you ever want to use some other version of Helvetica which also lacks a vendor code.

  2
• Dave Crossland Posts: 1,325

  May 2018

  For what its worth, at Google Fonts I disallowed foundry prefixes and suffixes, both because I don't want wacky sorting, and because a libre font project's contributors grows over time and the initial foundry may become totally disengaged, but if the family name has foundry initials then in this case it becomes awkward at best.
  
  There are a few families like "PT Sans" that were added before this policy position, and it isn't clear to me what to do about them

  5
• Thierry Blancpain Posts: 197

  May 2018

  I just wanted to check in here as one of the few foundries with a foundry prefix across their library. We don’t use typeface names that have been used for other typefaces without permission from the designers of the other typefaces, and have so far never done it to my knowledge. We renamed (pre-release) one of our typefaces after the original designer withdrew his previous consent to us sharing the name. So putting GT in our typeface names does not mean that we don’t respect other designers’ typefaces. 
  
  We keep the GT in our font menu names: GT Sectra is located under G, not under S. We have never had any customer come to us being confused about it – literally not a single support request in the 9 years since we started. Some customers, probably those who are more into design and type, understand that the GT in front of the name locates the typeface as part of our foundry, others might just think it’s a random bit of the name. It definitely, in my mind, creates a stronger coherence of a library versus single typefaces floating around MyFonts etc.
  
  One thing I’d want to stress in contrast with other responses is that what the type industry thinks of your naming scheme (or most other things) should rank very, very low on your list of decision-making criteria*. Your clients aren’t type designers.
  
  *To pre-empt what I expect to be an obvious response, that doesn’t mean you should behave unethically, it just means that the opinions of other font makers aren’t what should drive your decision. 

  9