Are all pictogram fonts broken in Lion?

Solution 1:

As Chris Redman said, the fonts are fine.

To access the glyphs in this font, you'll need to use the Character Palette.

Follow the directions he gave to show the Character Palette, then click on the Action button in the upper left corner of the window and choose Customize List…. Scroll down in the list and choose Dingbats, like shown in the image below:

enter image description here

Then choose the Dingbats category in the main window, then choose the appropriate font in the popup menu in the center column. The lightning bolt is shown in the image below.

enter image description here

As you can see, the Unicode value of that glyph is U+F07E, which is way the heck out of the range that you're going to be able to reach with your keyboard alone.

P.S. Both BBEdit and TextWrangler are Carbon-based apps. (Well, they could be hybrid, but the majority of the text-handling appears to be Carbon (HITextView?)).

Solution 2:

I think the fonts are fine - I've just checked them in Font Book.

I tried Text Edit, Pixelmator and Pages and they all do as you state. But, if you load Font Book and find the fonts they are visible and populated with "dings". Could it be that the codes are different due to using Unicode?

To get to Wingdings characters in the other apps:

  1. In Keyboard Preferences check "Show Keyboard & Character Viewers in menu bar".
  2. In the menu bar these is now a new icon.
  3. Click on the icon and select "Show Character Viewer".
  4. Characters can then be cut and paste from the Character Viewer.

Solution 3:

In apps that follow the unicode standard I think you should really not be able to type dingbats or webdings using the normal US keyboard layout (i.e. just change the font and type). The essence of the standard is that you no longer map pictographs (or anything else) to latin but give them their own codepoints, e.g. in the Private Use Area for web/wingdings and in U+2700 onward for dingbats. This ensures that the meaning of the text does not depend on the reader having a particular font active to translate the data.

The idea is that these characters should always be input via the Character Viewer or similar app (or a custom keyboard layout if you want to make one).

Nonetheless there is a large amount of legacy data which does map dingbats to Latin and fonts that reflect that are still in wide use. Also it seems that some Apple apps like Pages are designed to let you create web/wingdings via the US keyboard layout (though copy/paste to other apps will likely result in Latin text). Exactly how and why they do this I don't know.