FontLab Forum
2012-02-09, 03:50:10 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: Adding glyphs to a font after two years?  (Read 2453 times)
dzurn
Sr. Member
****

Karma: +0/-0
Posts: 6


« on: 2009-11-23, 12:27:07 »

We have some custom fonts that our company has been using for some time which we use for printing our labeling and manuals (at commercial print vendors, etc).

Now headquarters has commissioned a new version with some added glyphs to be used instead of some of the existing glyphs. No problem there, except that they didn’t change the name of the font and expect us to use and distribute the new version, noting “please copy over your old version”

What I see is that we will never know for sure if our print vendors are using the updated font or not, for any particular job. If the font had a different name, then we are all familiar with the “Can’t find the font” warning. But this updated-but-the-same-name font is deliberately sidestepping this mechanism. I can’t really see the logic here, besides some misplaced idea of compatibility with existing documents.

I can foresee getting missing symbols with NO warning if the old version is used, which wouldn’t happen with a new name.

I've asked this question before in other forums, but not gotten any feedback.

Basically, not renaming the font seems to me to be so awful that I am at a loss why it might have been done this way. What are the “redeeming qualities” of NOT renaming an expanded font? Has this happened "successfully" for a commercial font, besides the "Euro" debacle?

Horror stories from the lives of Service Bureaus would be appropriate to help them reconsider this policy. (And so when I DO rename the font when we use it, it will be a little more defensible than “I thought it would be better this way”.)

BTW, the font is an OpenType font with about 50 symbols, adding glyphs for about a dozen. The original symbols will still be in the font, but the new ones are alternates that we are supposed to use. Predominant use is in Adobe Creative Suite, especially InDesign, but there’s also a Truetype version for our on-demand Windows printing software.

Real-life stories appreciated!

Thanks
Darryl
Logged
Glagolitic
Sr. Member
****

Karma: +0/-0
United States United States

Posts: 15


« Reply #1 on: 2009-11-24, 01:09:10 »

Why not make a new style of the font with the same name? ie. italic?

Logged
BobH
Sr. Member
****

Karma: +0/-0
United Kingdom United Kingdom

Posts: 18



« Reply #2 on: 2009-11-29, 13:49:41 »

Well, as a counter-example, how many times have the core Windows fonts (e.g., Times New Roman) been expanded? (The answer: many times).  And of course the reason for not changing the font name each time is for compatibility with existing style sheets and templates.

I would expect that if the print vendor used the old font with a new document they'd get square boxes (or whatever you have in glyph 0) showing up in the output. Seems an easy enough thing to check for.

Bob
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!