🚀 go-pugleaf

I've got to say, Alan, your article just looks to me like a way to drum up business for your font-editing software by perpetuating myths about the way that fonts work on Windows and by potentially confusing and unnecessarily worrying non-typeface savvy users.

You say this is a problem that you have "encountered often" but you don't give us any actual example of it. Like Thomas, I've not had a problem with Windows recognising properly constructed fonts, and the only issue I'm aware of is due to having two fonts with the exact same name active at the same time. Of course, badly put together fonts or fonts edited by those who are not sure of what they're doing can cause problems (on PCs and Macs) but the answer is not more editing but avoiding such fonts in the first place.

To this end, I note your comment about an "impatient client [who] wants their document produced using Futura Condensed, and [who is] adamant that the fonts worked fine for their designer (who converted the fonts from Mac to PC just for you)". Not only is such forwarding of fonts almost certainly a breach of the font's license but such a workflow (having clients converting fonts from Mac to PC) is not one that professionals would recommend. Rather than advocating more editing, why not just tell people to use OpenType fonts?