Keyboard mapping a font?

[angelize]

I have a question regarding Type tool 3 I am still playing around with the demo, but I am wondering if it has an option to let you set what restrictions you do or do not want, such as if you want to allow embedding

[Gare]

I just ran the demo, and then brought an exported typeface into FontLab.

It tells me that it is: Only Previewing and Printing is allowed (read only), which means you can send it out to the web via WD MX if this is what you're asking, but the demo is so crippled I would only do this with a registered copy Frances. The exports have "FontLab", "FL" violations in the center of the glyphs.

-g-

[mwenz]

Frances,

I do not believe that TT has any options to set restrictions. Therefore, the font can be pretty much used for anything (usual caveats) like most every one of my installed fonts.

Take care, Mike

[Gare]

On that note, how does the average person tell what restrictions are coded into a typeface?

I realize that none of the tg members are average, but seriously: FontLab can reassign permissions and tells you the current restrictions on any font one loads, but that sort of begs you getting FontLab.

And I'm not sure the test I ran will hold up if you buy the commercial copy. Mike, is there a page like this is the commercial version or not?



BTW, nice, clean avatar, Mike! I like the warm and cold muted colors workin' with and against each other.

-g

[mwenz]

Hi Gary--not that I can find. And the PDF help file does not shed much light other than to discuss formats that allow/disallow embedding restrictions, etc.

Windows Explorer shows relevant information:



MainType (and likely other font managers) show embeddable status.

Here's the relevant (and only) screen from TT for font parameters:



Take care, Mike
(thanks)

[angelize]

Hi guys, thanks for your responses, I was wondering about being able to embed a font created with TT in a website created with WDMX.

[Gare]

The answer is "yes", Frances, but not necessarily, "Yes, you should."

There is literally no difference in coding between a font you create and any other font you want to embed using Web Designer MX. So in practice, it works.

But just as you need a compelling reason to post a 5MB JPEG image on a website, you need a compelling reason to (sometimes marginally) slow down the loading of your website, if it's "glamour factor", and you don't have a solid artistic and/or commercial reason for embedding a typeface.

The way a font destined for the web needs to be crafted takes time, skill, patience, and a little learning. The very first thing you need to know is about unit height and how a typeface displays on a webpage. If, for example, you build a font whose cap height is 627 units, I think you might be able to image how the font will render onscreen at 12 or 14 points. "The math is wrong", and you'll probably get a line of pixels within the font that is unwanted because the web browser can't reconcile the math.

You are also well-advised to pack everything you can imagine into a typeface used on the web. For example, on the Xara Xone, one of the fonts has a complete set of bulleted numbers and other glyphs you see all the time done as GIF bullets. This means that only one fetch needs to be done to get the font and a lot of the re-occuring dings we have on the pages.

And I'm not an expert on this stuff, but I do know how to do web fonts inexpertly and just plain wrong. I'm still working on one of the fonts we use, the hinting isn't quite right, but all website building is a WIP anyhow, isn't it?

My Best,

Gary