Can I use a particular font (my wife is very fussy - Cochin regular) for a website which is not graphic (ie html) and that will display correctly on all computers as Cochin and not be converted to Verdana/Helv/Times etc when viewed.
So what you’re saying is that even with the Caxton action, I’m not guaranteed the user will see Cochin as there are fall back fonts. Is the only way to guarantee it by using graphic text?
The Caxton Action will guarantee it will be used (in all modern browsers), but you’d need to buy a license to use the font in that way. The Action puts the font on the web which essentially makes it publicly accessible for anyone to download. It’s copyright infringement if you don’t have a license to use it in that way (i.e. you use the font that’s installed on OS X).
You can purchase it here:
Hope that helps,
Joe
On 12 Jan 2012, at 15:39, scoutdesign wrote:
Thanks DeltaDave and Joe,
So what you’re saying is that even with the Caxton action, I’m not guaranteed the user will see Cochin as there are fall back fonts. Is the only way to guarantee it by using graphic text?
Hmmm - OK here’s what I do without any warranty of being on the “safe and legal side of life”.
Seeking Google WebFonts for a nice font. Probably there is one comparable to Cochin. Download this to get the .ttf and install it on my system. In Freeway (restart it to get the Font in the list) I build a new Font-Set (most without any fallback) as recommended so I can use it.
At least I tried a lot including Caxton but WebFont Action is so simple and at least as cross browser as it can be (even IE8) while I had with all other methods much trouble to get it run.
A warranty of displaying FONTs as expected on each browser can’t be given anyway cause you can’t be sure what people are doing out there.
The non-legal way:
you need Cochin as .ttf so you can convert it to .eot using ttf2eot on the web!
The legal one:
You purchase both types (print and weblicense) - and apply it as written above.