OK - after a couple of hours of reinstalling, Archive and Installing, and generally trying just about everything, I figured it out. Here's what happened:
Apparently in Leopard (os 10.5) fonts with Special Characters (alternate language glyphs like Arabic, "Dingbats" and other symbols, etc) have those Special Characters stored in the correct Unicode group of the font, and NOT in the regular / Latin area. So previously, where I was used to pressing "b" in Zapf Dingbats and getting a certain compass symbol, that symbol is now located elsewhere in the font, and can only be located using the Character Palette.
Note that this is not consistent across applications: TypePad behaves like this, LiveType does, but Microsoft Word doesn't. I'm guessing it has something to do with the quality and consistency of Unicode support. Not only that, but LiveType doesn't let the Character Palette change the current font correctly, so getting just the right symbol into the track can be challenging.
This is
incredibly confusing, and
incredibly poorly documented. Google searches for lost fonts, lost characters, etc turned up nothing, and Apple's own documentation was woefully incomplete in this area. I know this is the "correct" way to do it, but a little heads-up that such consistent workflows, used for years, would change would have been a nice thing to know.
Hopefully this note will help others in a similar situation.