Some of the characters have different places in Windows and Mac character charts, especially in what are called "high bit" characters which lie beyond the official ascii range. Using a keyboard diagram or a utility (like KeyCaps on the Mac) would show you where some characters might be found, but in the past I've had to build an alternate font in Fontographer to access some of the characters that are encoded in the font but not accessible from the keyboard.
Unfortunately, Quark doesn't respond to Unicode characters as such or I could have used that; when I asked Quark about it last year they said the program would have to be rewritten to take advantage of Unicode (I would use it for foreign characters, probably).
If software developers, font producers and operating systems producers would agree to support Unicode, we could access all these odd characters (including foreign characters) with much less hassle.
Right now, Microsoft seems to support it, and Apple supports it if the software developer puts in the right code to deal with it, but I do wonder if we would all have to buy new fonts to take advantage of it.Maybe some day, when they aren't all busy protecting their domains from possible competition and start focussing on usefulness.
