Font Forum

Another cause of the problem might be the presence of the LTSH table. If a glyph is added to the font this table should either be updated (which FC cannot do) or deleted. If an LSTH table has incorrect values the added characters will space unpredictably.

Give your font a new name (say, Arial Bold only) and save it under a new file name. Make sure the font is marked as Bold. If not, Word will use its own mechanism to make it even bolder when you apply the Bold attribute to the font.

vanisaac wrote: And his name is Erwin, not Edwin.

You're sooo right...

Perhaps it's useful to explain the purpose of these tables. If I'm correct they are not vitally important. A font can work properly even if none of these tables is present. Yet they are certainly useful, because they reduce the workload of the rasterizer. When a text is written to the screen the ras...

No doubt you're right. Microsoft's most recent font, Tahoma of XP Service Pack #1, still has a number of glyphs with intersecting contours, but far less than Arial.

As far as I know this is true for both simple and composite glyphs, which is why FC flags both of them. You'll notice in professionally made fonts that glyphs with overlapping components (like c cedilla), which could be made quite simply in a composite glyph, are in fact simple glyphs *without* inte...

Yes, just copy a horizontal line from another glyph and paste it on top of the D. But please note that intersecting contours are non compliant with True Type specifications. That's why they are reported as errors by Font Creator. This doesn't mean that this kind of glyphs don't work properly. They d...

The workaround doesn't change the proportions of the glyphs. It changes their height *and* width. As far as I know there's no way to change only the height or only the width of all glypohs in a font at the same time.

Perhaps you're trying to save the font to the WINDOWS/FONTS folder. Try saving to a different folder.

Mike, thanks for keeping me posted. Well, apparently that's the way Microsoft treats her customers. First, they deny there's a problem. Then they say it's someone else's fault. When proven wrong they maintain an eardeafening silence. In my view the most sensible thing to do is finding another locati...

Mike, Could you keep me posted on this subject and MS Support's reaction? Microsoft Keyboard Layout Creator has severe limitations in creating dead key sequences. The trouble is that these limitations *don't* show when testing the keyboard within KLC; only after compiling and installing the keyboard...

I was partly wrong: Microsoft apparently *did* document its use of PUA. I found this site
http://scripts.sil.org/cms/scripts/page ... orUseOfPUA
which provides a quick overview of the ares used by Microsoft and links to Microsoft pages.

I'm quite sure there's nothing wrong with the font. I'm afraid it's a Microsoft Word issue. I have the same problem after using Microsoft's program to create a keyboard. Apparently the programmers of Word usurpate the Private Use Area for their own purposes (they'd better check the meaning of 'priva...

I mean a list of Unicode code points assigned to glyphs within the font, preferably together with the glyph's number in the font.

You're right on the other issue: this is only true when copying within the font.

Two remarks:

- When you copy and paste a complete glyph (or a number of glyphs) hinting is preserved.
- As an alternative to glyph sorting it would be a nice feature if FC could produce a list of characters present in a font. This would make comparison even easier.