Office 2008 Fonts - Best Management Techniques
hi, manage our fonts extensively (using suitcase fusion), , bare minimum system fonts left handled system. use lot of our own fonts override system fonts, etc. keep real clean.
so got new ms office 2008 suite. comes 130 fonts. lot fonts have. .ttf versions of postscript fonts have. upgraded versions of fonts shipped previous versions of office.
- have handle , management strategy of these fonts?
- how preference keeping our postscript versions vs. tt fonts included? i've heard fonts included unicode. value?
we not want have multiple versions of same fonts. in past our postscript versions of fonts more complete, having greater range of weights, etc. don't know if office apps need unicode functionality of these new tt fonts.
we prefer use opentype fonts exclusively going forward, can't purchase yet 3rd version of these crazy fonts.
any ideas???
so got new ms office 2008 suite. comes 130 fonts. lot fonts have. .ttf versions of postscript fonts have. upgraded versions of fonts shipped previous versions of office.
- have handle , management strategy of these fonts?
- how preference keeping our postscript versions vs. tt fonts included? i've heard fonts included unicode. value?
we not want have multiple versions of same fonts. in past our postscript versions of fonts more complete, having greater range of weights, etc. don't know if office apps need unicode functionality of these new tt fonts.
we prefer use opentype fonts exclusively going forward, can't purchase yet 3rd version of these crazy fonts.
any ideas???
office 2007/2008 (and vista) come brand-new typefaces, of start "c." full set calibri, candara, constantia, corbel, cambria , consolas. these opentype fonts truetype outlines (at least on windows - i'm assuming ms shipped same fonts mac os.) of these default fonts office and/or vista.
i can't guarantee office not rely on other fonts, don't think so.
for cases ms-supplied fonts conflict ones have, i'd keep ones have compatibility reasons, unless ms-supplied ones have obvious advantage (such bigger family).
truetype , opentype fonts use unicode encoding. clearer , more reliable way apps , oses associate characters glyphs, not absolutely necessary. in particular, using unicode encoding not mean font has more glyphs (or encoded characters). truetype , opentype fonts *can* have more language coverage, doesn't mean given font does. opentype fonts (with either kind of outlines) can have added typographic features using alternate glyphs, again don't *necessarily* have them.
note "c" fonts mentioned earlier have both added language coverage , nice typographic features (such oldstyle figures , true small caps).
regards,
t
i can't guarantee office not rely on other fonts, don't think so.
for cases ms-supplied fonts conflict ones have, i'd keep ones have compatibility reasons, unless ms-supplied ones have obvious advantage (such bigger family).
truetype , opentype fonts use unicode encoding. clearer , more reliable way apps , oses associate characters glyphs, not absolutely necessary. in particular, using unicode encoding not mean font has more glyphs (or encoded characters). truetype , opentype fonts *can* have more language coverage, doesn't mean given font does. opentype fonts (with either kind of outlines) can have added typographic features using alternate glyphs, again don't *necessarily* have them.
note "c" fonts mentioned earlier have both added language coverage , nice typographic features (such oldstyle figures , true small caps).
regards,
t
More discussions in Type & Typography
adobe
Comments
Post a Comment