Posted By: jamie | Jun 15th @ 1:42 PM
page 1 of 2
Comments: 30 | Views: 741

quick idea about fonts ... on the web.

Q: why not include 2000 fonts with win7 (or partner with corel to do it)

?
It sure would bug Adobe.. and SteveB could announce:

" Fonts for all - now with windows - the web has opened up to real publishing!" *when using IE

there could be Font packs rolled out as well - for sure one containing Segoe - entire family
(in the old days - MS pushed for fonts on the web - first with weft etc)

lets go ms! fonts on the web! win7!  ?

 

Harlequin
Harlequin
http://twitter.c​om/TrueHarlequin

Bill Hill went into this in his last interview. It's not about getting web fonts on Windows 7, it's about setting a standard on font embedding. Microsoft already has the best one out there, needs to be ratified.

stevo_
stevo_
Human after all

Jamie if you are wanting to embed custom fonts into webpages, this is becoming pretty realistic, you are limited to a degree (more so with IE) and also legally but its certainly starting to happen as browsers race towards implementing css3 features.

figuerres
figuerres
???

Adobe never "owned all the fonts" not by a long shot.  they had a set of outlines that went with the PostScript engine yes but that was 36 faces.

Type Faces are owned by the creator / Type Foundry ... Like Monotype for example.

now if you look at a catalog of many faces most of them are just slight variations on a few of the classic ones like Times or Helvetica.

I think really that "the average joe" will generally not even see the differences between many of the faces out there.

so this brings up the question of how much benefit to how many users at what cost?

Now I think that a set of faces like the classic 36 PS faces would have a good value .... but not 2K or more.

aside from that IMHO if you feel strongly on this get with Bill Hill and the WC3 on the standards for FontEmbeding in html.

I do think that getting all the major players in line on that would be great -- down the road we could see less giant jpegs on pages just to spell out one or two words like say "Shell" or "Microsoft" or whatever.... and that would also make them searchable and more userfull for the blind etc...

PS: Faces NOT Fonts,  you should licence a face and then have the rights to use that face in all it's forms. you do know that yes?

PaoloM
PaoloM
Hypermediocrity

If all you want is "ie only", then you just need WFET3 and any font of your choice.

Problem solved.

Next!

Harlequin
Harlequin
http://twitter.c​om/TrueHarlequin

There is also SiFR and others like it. Uses Flash to write out the font, even selectable as text too. Problem is, again, you're back to licensing issues. Subscribe to the "i love typography" blog, to see how much work people actually put into making fonts. I think the same mentallity needs to go towards having music embedded in your page.

PaoloM
PaoloM
Hypermediocrity

I love SiFR, but you're right. Fonts should only be used for the purpose they were licensed.

figuerres
figuerres
???

well sorry but i think that

1) *if* msft were to do the "2000 fonts" they would have to cover the messy licensing costs - you may not see this is a big deal but it is.

2)  Next comes the law suits that would follow this... even if they were without merit msft would have to deal with the costs of them.

3)  "IE ONLY" would be non-enforcable - it would have to be windows, any app that runs on windows.

4) why?  again what is the benefit to 90% of the users of windows ? sorry but as far as i can tell this costly idea only benefits a small number of the userbase.

like i said just get a good set of faces for the os and then get on the standard.

for MSFT the winning press angle (IMHO)  is to work with the standards body and show MSFT as a fair player in the WWW / W3C. Push the "We do not want to be the evil giant of the software world" that would give Mr. Steve a good story to push that would clearly put MSFT in a positive light.

And let's not forget that there are other OS'es and Browsers out there, they are not going to all disapear next year... so a standard that gets better type into more browsers means that web designers have a clean way to build better sites that will "just work" for the customer.  the desinger should not have to make 2 versions of a site one for windows and another that looks worse for everyone else. thats the wrong way to do it. if you want to "Publish to the WWW" that is.

brian.shapiro
brian.shapiro
things go on as always

I'd like Calibri more than Segoe to be a standard Web font. Calibri is like the sans serif version of Georgia

 

PaoloM
PaoloM
Hypermediocrity

Did you even bother to read the link I posted?

Expressionless

PaoloM
PaoloM
Hypermediocrity

thats embedding - im talking ( hoping) for local

What is the difference? I mean, what's your goal? Do you want to be able to define precisely the font that the user will see? Then embedding is perfect.

Why does the user need to have the font installed?

Sven Groot
Sven Groot
My name has 9 letters. Coincidence? I think not...

no ordinary webpage maker uses embedding.

Then we need to improve the tools so that they do.

I certainly don't want to waste disk space on 2000 fonts that I'll hardly ever use.

blowdart
blowdart
Peek-a-boo

if there were one thing youd WANT windows to install -(after itself)  wouldnt it be fonts?

No, I'd rather have functionality installed than give ammunition to pathetic little web designers who think fonts are the best way to express their creativity.

PaoloM
PaoloM
Hypermediocrity

I give up.

I have no idea what you're saying most of the times anyways.

page 1 of 2
Comments: 30 | Views: 741
Microsoft Communities