Pages for iPad cannot create usable PDF files

Some PDF files from Pages for iPad are distorted or unreadable when opened in Adobe Reader. They display much better in Preview, but as Windows users do not have Preview, this is not much of consolation. You can follow this thread to see other people having the same problem. If Apple releases a fix, the thread is likely to be updated by happy users.

There seem to be some dependency on which fonts are used. Trying out most of the fonts installed on my iPad, hardly anyone displayed correctly in Adobe Reader. However, all except Heiti and Zapfino were readable. Heiti and Zapfino displayed as dots: ••••


One font actually displayed as it should, and that was Apple Gothic. It is a mystery why that one of all fonts worked.

Most other fonts displayed as Adobe Sans MM. To get a consistent layout, you can try using Arial or Helvetica in Pages for iPad, as they also are sans serif fonts. You can also try Apple Gothic.

It is nevertheless good to validate the file in Adobe Reader. The final display may depend on your system or the layout of the document.


A list of embedded fonts in Adobe Reader. File > Properties > Fonts.

TextEdit and Styles

In case you use TextEdit as well as Pages, you will have noticed that TextEdit has an unusual and sometimes buggy way of handling styles.

If you click on the "Styles" control in TextEdit's toolbar, you will at first only see Favorite Styles.



A Favorite Style can be used in any TextEdit document for this user on this computer, but nowhere else. It is stored in the hidden file .GlobalPreferences.plist.

If you click on "Other...", you will get to a window where you can see the Document Styles. In contrast to almost all other programs, a Document Style in TextEdit has no customisable name.



It just contains some sample text ("ONE" in the picture above), which has a particular format. All formats used in the document appear as you click the arrows back and forth.

To create a Favorite Style from the current format, click on the button "Add To Favorites" and give it a name, and choose if you want the font and ruler information to be part of the style.

To delete a Favorite Style, click on the radio button Favorite Styles, select the style you want to delete and click on Remove From Favorites.



If you click on Select, you can choose to select where the style is used, based on different criteria.



You click on Apply, the active style is applied to the currently selected text.

Done in the Style window just closes the window.

If you do not have the Ruler active, you can still use Styles with the menus: Format > Font > Style

There is no easy way to edit an existing Favorite Style. The steps are:

1. Apply the style to some text.
2. Modify the text to the new format you want.
3. Add the new format as a new Favorite Style with the same name as the old style.
4. Accept the warning that you are replacing an existing style.

There is no way of telling which style is applied to a particular piece of text. That information is not stored and not displayed.

Personally, I think it is questionable if TextEdit's styles are better than no styles at all. It is clear that there has been some development effort, but the design does not seem to have gone through any usability tests. Still, if they fulfill any of your particular needs, there is of course no harm in using them.

Print shops and embedded fonts

With some print shops you may get an error back saying something like "This file was created with Mac OS X 10.4.11 Quartz PDFContext / Pages. We cannot print files created with this application."

Mac OS X embeds several subsets of the same font, just like many other applications. However, for some reason some printers (like Lulu) are not able to handle the way Mac OS X does it.

A solution that in some cases works is to create the PDF using Print > PDF > Print to PDF-X. In contrast to a standard PDF, which can be used for many purposes, a PDF-X file is dedicated to facilitate printing.

You can find some more information at the following sites:

• http://athleticaid.com/yaquinapress/PDF-FAQ.html#Mac_PDF_issues
• http://www.lulu.com/en/help/index.php?fSymbol=reasons_files_dont_print
• http://www.prepressure.com/pdf/basics/osx_quartz
• http://www.lulu.com/forums/viewtopic.php?t=25428

How do I type Wingdings in Pages?

Wingdings and Webdings are fonts with small images instead of the letters. My personal recommendation is that you do not use them, even if you have the fonts. This is why:

Every document you type will be read by someone - either by someone else or by yourself in a few minutes, days or years. A document you type with Latin letters or any standard unicode letters is likely to be legible by anyone with the right software - today and in the future. But Wingdings is not standard unicode.

Now, let's assume that you want to show the yin-and-yang symbol to a reader.


You know that it is part of the Wingdings font, so you decide to get the symbol there.

So what you can do is to activate the Keyboard Viewer. Then select Wingdings from the menu in the bottom left corner and then select Wingdings as font in Pages and start typing.


However, when you send this Pages document to another computer user, it is very possible that he will not have the Wingdings font, so the character will not display. What is displayed is just "[" because that is the character that Wingdings uses to display the yin-yang symbol.

And the same thing can happen to you. When you change the paragraph style in this document, the symbol will become "[". If you copy the text to another application, it will become "[". If you export it to RTF and then open it in TextEdit, it will become "[". It is basically a very unstable character - just like all other characters in Wingdings, Webdings and Monotype Sorts.

TextEdit does not even allow you to type the character, and that is probably a wise choice. You can insert it from the Character Palette to TextEdit. You find it in the Character Palette with the View PIFonts, Font: Wingdings-Regular. However, what is inserted is the unicode F05B which is in the Private Area. The Private Area means that it can be used by anyone for anything, so depending on the available font, it can appear as completely different characters.


As you do not know which font the reader will have available, you will not know what the document will look like to him. That's why it usually is best to avoid Wingdings fonts altogether.

There are perhaps cases where you need to use them, but try to make sure you have a normal picture as a backup - just in case. You can also use Wingdings to create PDF files, as PDFs usually embed the font.

How do I select all instances of font X?

Paste and run the following script in Applications > AppleScript > Script Editor:

tell application "Pages"
 select (every character of body text of front document whose font name is "Times-Roman")
end tell

Note that the font name may not be what you expect. The script above searches for the font "Times", even though the name in the script is "Times-Roman". If you type just "Times", it will not work.

If you need help to see what font name AppleScript expects, mark the first word of Pages front document in the desired font, and run this script:

tell application "Pages"
 display dialog (font name of word 1 of body text of front document as string)
end tell

(Sorry for the bad formatting above. Blogspot is not made to display source code. However, even if you cannot see the last characters on all rows, they should paste fine when you copy them.)

Why did Pages' characters look blurry?

With Pages 3.0 and earlier, many users perceived problems with blurriness around the characters. With Pages '09/Pages 4.0 Apple changed the way fonts are rendered, which makes them look darker or sharper than they did before.

The word below is written using Helvetica 10 and rendered at 100% size. The top rendering is Pages '09 and the lower one is Pages 3.0. Surprisingly the top rendering looks better on an LCD screen than the lower one.



This uses the default setting in System Preferences > Appearance > Font smoothing style. With Pages '09, this setting is taken into account, unlike previous versions.

If you want to turn font smoothing off, open a terminal window and use the command

defaults write com.apple.iWork.Pages SFRFontSmoothing 0

If you want to turn it back on, use the command

defaults write com.apple.iWork.Pages SFRFontSmoothing 1

The text below was written for previous versions. It contains more explanations of what was wrong.
---

Most letters have some round curves, and that is a problem, as current computer screens consist of a lot of small dots, not curves.

The process of mapping the round curves of letters to pixels is called font rasterisation. There are different strategies to do it.

Last millennium one of the most common strategies was to simply put black dots in logical places. AppleWorks uses that method, and the result is that the letters get very rough edges. Here is the word "lollipop" written in Helvetica, 10 in AppleWorks. It is magnified about 10 times, so you can see the pixels.
The next strategy was to use anti-aliasing. That means that you add pixels of different shades of grey to increase the illusion that the letters are curved. It looks ridiculous when you magnify it, but when the font is small, it is surprisingly efficient. It is very likely that your web brower uses anti-aliasing to display the characters you read right now. Magnified, the characters do not look very legible:

But on a screen, it does not look quite that bad:


This is still the most efficient strategy, if you have a CRT (Cathode ray tube) screen. It is also the method Pages uses. However, fewer and fewer people use CRT screens nowadays.

For LCD screens, the best strategy is usually subpixel rendering. This uses the fact that each pixel on an LCD screen consists of three small elements, one red, one green and one blue. Looking at a magnified image of these pixels gives the impression that it is almost illegible. However, when one takes into account that the colour elements are at different positions inside each pixel, it is easier to understand that this can actually be easier to read than plain anti-aliased text.

On the screen it looks a little better. Keep in mind that this is my screen magnified about 10 times.

As you can see, the monitor does not simply display the colours right off, but there is some algorithm how to display it correctly.

To some people this gives a much clearer picture. To others it is mostly annoying, as they are able to see the different colours, in spite of the small size. This is a technology used by for example TextEdit and MS Word for Mac. Your browser may also use it.

Using System Preferences > Appearance, you can change this setting for TextEdit and Microsoft Word and many other applications. If you choose CRT, you disable the subpixel rendering in the applications.
However, these settings hardly change anything at all for Pages.

Why does Pages not allow subpixel rendering? The most convincing explanation may be that it is more difficult to implement in Pages than in other applications, as text can be transparent against a coloured background. It would be very difficult to choose how to handle transparent coloured pixels, when the background changes colour.

Besides, the number of pixels per inch increases all the time with more modern screens. In the near future, it will not matter much which technology is used to map curves to pixels.

So, what can one do, if one thinks Pages displays too blurry characters on the screen today?

Not much. One can either get used to it or buy a new screen with higher resolution or simply increase the zoom.

If you want to learn more about font rendering in Mac OS X, here is a list of facts and opinions on the subject:

• Font smoothing in Pages: It’s about text transparency
• Vista puts Mac OS X font rendering to shame
• Font Rendering: Respecting The Pixel Grid
• What's Wrong With Apple's Font Rendering?
• Font rendering philosophies of Windows and Mac OS X
• Font smoothing, anti-aliasing, and sub-pixel rendering
• Safari is better in Complex Unicode Font (Sub-Pixel) Rendering

And after Pages '09

• Pages ’09: Two significant breakthroughs

How do I best organise my fonts in Fontbook?

You may have read in some obscure blog posting that it is good to organise your fonts in Collections in Fontbook. That obscure posting was right, but what strategy should you use to create collections? Which criteria should you use?

You should of course create one or a few folders with your favourite fonts, based entirely on what you like.

In addition, it may be good to create folders based on some objective criteria, and to do so, you can often use the search field.

You can for example start with a search for fonts that contain Italic typefaces.

1. Create a collection called "Italics".
2. Type "Italic" in the search field. The font list now only contains fonts which match the word Italic.

3. Select all fonts with command-A.

4. Clear the search field. The selection now extends to all typefaces in the fonts that contain italics.

5. Drag the selection to the collection "Italics".

You now have a collection with fonts that you can italicize ready to be used in Pages or TextEdit or any other application using the Font Palette.

But you can go on.

6. Create another collection called "Italics Slimbach".
7. Click on the Italics collection and type "slimbach" in the search field and repeat the steps above.

You now have a selection with fonts by the designer Robert Slimbach, which all contain Italic typefaces.

And on again.

8. Go through the steps above again, but this time use the search word "Russian".

And you have a collection of Slimbach's fonts that can be used in Russian with Italics.

You can go on like this and create collections with more and more detailed criteria in different areas. You can for example search for "Apple" or "Adobe" to find fonts from those companies. Or you can search for OpenType or Postscript.

There are, however, two things that seem impossible to search for reliably: non-proportional fonts and sans serif fonts.

If you need that you need to create the collections manually. But there are still quite a lot of different kinds of collections you can create using the search function.

OpenType, TrueType, PostScript fonts, which is best?

A new well designed OpenType or TrueType works fine with Mac OS X 10.5 (Leopard), and most people have no reason to ask themselves any questions - at least not if you write in a language with a Latin alphabet. Older fonts may not work in Mac OS X 10.5, even though they worked in 10.4. As PostScript fonts are being phased out for OpenType fonts, PostScript fonts often tend to fall in the unsupported category. Mac OS X supports Macintosh or OpenType Postscript, but it does not support Windows Postscript.

Here is a short summary for each font.

• PostScript fonts are nowadays almost always Postscript Type 1. There are plenty of other Types, but none of them matters. Some features (like the hinting) are not completely documented. They are defined with cubic Bézier curves which is more flexible and more complicated than TrueType's quadratic curves. The reason they exist is that Adobe created them. As Adobe now promotes OpenType instead, it is likely that pure PostScript fonts will become rare.
  
• TrueType fonts were developed by Apple and licensed by Microsoft. They use quadratic Bézier curves. The reason they exist is that Apple and Microsoft did not want to pay Adobe's high license fees.
• OpenType fonts were developed by Microsoft and Adobe. They are a thin wrapper around PostScript and TrueType fonts and share the same features. The reason they exist is that Microsoft and Adobe wanted one unified format.

Most fonts work equally well on both Mac OS X 10.5, Windows and Linux, but there are exceptions.

OpenType support is much improved in Mac OS X 10.5 compared to Mac OS X 10.4 (Tiger), but it is not yet complete. Most typographic extras now work as well as they do with TrueType fonts: ligatures, old-style figures, contextual alternates and so on. Even the Japanese glyph variants work as well in OpenType as they do in TrueType.

However, some glyph variants still do not work in Pages; exact line spacing does not work; and Arabic ligatures do not work at all, even though they work in TextEdit.

What is a "rare" ligature?

If you open the Typography panel from the font panel, you may notice that some fonts have both "Common Ligatures" and "Rare Ligatures". What is that supposed to mean? Is it not up to the user to chose what s/he thinks is rare or common?

There is no strict border between common and rare ligatures. The base assumption is that a common ligature is a ligature that is natural and can be applied without disturbing the text. Take the ligature fi mixing f and i. You can usually apply it whenever an f and and i meet. Most readers will hardly notice, but the text becomes more pleasing to the eye. Common ligatures are usually switched on by default. Common ligature very often start by the letter f. Some good candidates for common ligatures are ff, fl, ffi, fi, ffl, fb, fk and fh.

A "rare" ligature, however, goes out of its way to be noticed. It is usually pleasing to the eye, but at the same time it is so obvious that it disturbes the reading. They should usually not be applied to body text, but they can be applied to headers and titles. The most common "rare" ligature is probably st for s and t. But there are many others. Apple Chancery has rare ligatures for the letter combinations ot, et, sp, ss and es, just to mention a few. Big Caslon and Hoefler Text and many Adobe fonts provide rare ligatures for ct.

Overuse of rare ligatures in Apple Chancery.

The recommendation is to leave the default - common ligatures on, rare ligatures off, unless you find a really good reason to change it.

More information for ligature enthusiasts.

How do I change the shape of the Font palette?

The Font palette or Font panel, that little friendly window that comes up when you press ⌘-T, has a surprising number of possible shapes. Some you can get by simply resizing the window from the lower right corner.

Drag up left:


Drag up right:


Drag down left:


Drag down right:


And then access the wheel menu, where you can show "Preview" and "Effects":

With Preview:


With Preview and Effects buttons:


You can also mix them to some unusual but perhaps useful combinations, like Preview in a really small window.

How do I change kerning in Pages?

You cannot, and that is mostly a good thing. However, you can change tracking using the Inspector > T > Text > Spacing > Character. And that is probably what you want to do anyhow.

The following paragraphs are just there to get the terminology right. If you do not care about the terminology, you can skip the rest of this posting.

Tracking is a fairly simple thing. It is just the space between the characters.

Kerning, on the other hand, is a property that is built into the font itself. It defines how certain characters are adjusted when they stand next to each other.

The two bottom fields in the picture above show kerning and tracking in Adobe InDesign. Here the kerning is shown as -37 within brackets - the default value for kerning between W and A in this font. Nothing is changed by the writer. The tracking is 100 - also the default.

As W and A lean in the same direction, they can stand slightly closer than for exampel W and T without touching each other. -37 expresses how much closer they can be according to the font designer.

Between A and T, the default kerning is -74. The font designer decided that they could get even closer to each other.

However, between T and E, the default kerning is 0. There would be no advantage pushing them closer together, as they already are very close on the top part.

Usually the default values are good, and you would not like to change them.

However, if you really feel you need to change the kerning instead of the tracking, you can use TextEdit. To see how it works yourself, create a new document with just two lines:

WA
TER

Highlight the text and go to the menu Format > Font > Kern > Use Default. Now look carefully at the letters and go to Format > Font > Kern > Use None. You will see that WA changes, but not TER, where there is no default kerning.

The same trick does not work in Pages, where the similar menu is Format > Font > Tracking, and the options are None, Tighten and Loosen. This is just a round about way to do the same thing as in the Inspector - tracking.

Pages adjusts tracking - not kerning. And to most of us tracking is just what we need.

How do I see what my fonts look like?

From Pages '09, you can see WYSIWYG font previews in the Format Bar font menu. Just make sure that you have the preferences right: Pages > Preferences > Show font preview in Format Bar font menu. To switch between WYSIWYG and standard font names, hold down the alt-key, as you click on the menu.

In previous versions this was not possible, but there were some other options that worked fairly well - some would say better.

Use the Font palette header

Follow these steps:

1. Display the Font palette using ⌘-T or the menu Format > Fonts > Show Fonts.
2. Click on the wheel in the lower left corner and choose "Show Preview".
   

You will get a preview of the currently highlighted font.

To easily scroll between the fonts, first put your cursor in the search field. This will take the focus away from your main document. Then highlight a font and scroll up and down with the arrow keys.

Use the Font palette Favorites


Select the collection "Favorites". It lists the latest font families you used, and it shows them in the last used Typeface and Size.

Use an Apple Script

Follow these steps:

1. In the Finder, go to Applications and open Font Book.
2. In Font Book, highlight all fonts (or the ones you are curious about).
3. In the Finder, go to Applications > AppleScript > Example Scripts > Font Book and double click on Create Font Sample.scpt. It will open in Script Editor.
4. In Script Editor click on "Run".
5. Wait.

After some time, you will have a document in TextEdit that contains samples of all your Typefaces in all your fonts. Save it for future reference.

Use Font Book

Font Book is an important tool for at least two purposes. One - display what your fonts look like. Two - organise your fonts.

The main reason Apple has not included WYSIWYG font displays in Pages or the Font Palette is that it would be next to impossible with all the fonts we have today. You would have to scroll for ever - up and down, looking for a font that fits your needs. You would forget the name of one you saw and you would have to start over again.

WYSIWYG font menus worked on the first Macs, when the average user had no more than six fonts, but today the average user has several hundreds.

If you are serious about finding the most perfect font in this hay stack, use Font Book collections. It does not cost anything, and they are easy to remove, when no longer needed.

Create a collection for for example sans serif fonts, another for good body text fonts, another for Chinese fonts, and so on. It will be much easier to compare Monaco and Andale Mono, if they are in the same small collection, than if you have to scroll 150 fonts to get from one to the other. For more hints how to create collections, check this post.

Helvetica Narrow problems

With Mac OS X 10.5, Leopard, some users report problems with Helvetica Narrow appearing as substitute font for Helvetica. There are couple of things you can try to fix the problem.

* The obvious thing is to delete Helvetica Narrow. Also look for "N Helvetica Narrow", which may be stored in one of the font folders. Spotlight search for the fonts, to be sure to find all instances.

* Disable Helvetica Narrow. That seems to have worked for some people, but not for everyone.

* Install Helvetica a second time, but this time to your User library or /Library/Fonts. You can find the font using Spotlight. Drag it to your User library or /Library/Fonts or use Font Book. If you get a warning about a conflict, choose "Allow Conflict". (This is not a very clean solution, but it has worked for some people.)

* Disable all your User fonts - just in case.

* Remove all System 9 fonts from /Library/Fonts. You can recognise them as they appear with a size of zero.


For other font problems and suggested solutions see deleting font cache and missing fonts.

Update 29 May 2008: The updated version of Mac OS X, 10.5.3, is said to fix the Helvetica Narrow problem.

My fonts in Leopard are crazy. How do I reset the font cache?

In the best of all possible worlds, you should never have to reset the font cache, but Leopard (Mac OS X 10.5) seems to have some stability issues with fonts, which sometimes appear missing, even though you can see them in Font Book. If you have serious font problems, you can try the following. It is (probably) risk free if you follow the instructions exactly, but if you do not follow them to the letter, you may damage something in your system.

Therefore you should only follow these instructions in two cases:

• You understand them perfectly, and you know what they are doing.
• You are desperate because of some font problems.

Here are the steps:
1. Open Terminal.
2. Type the following two commands:

cd `getconf DARWIN_USER_CACHE_DIR`
open ..

3. In the Finder window that appears, drag the folders -Caches-, -Tmp- and TemporaryItems to the Trash, if they exist.
4. Restart. You may get a message that the boot cache is being rebuilt.

Once you have restarted, your font problem may be gone.

For other font problems, see missing fonts and Helvetica Narrow.

How do I use an image to fill text?

There is no built in way of doing it, but if you have some time it is possible using Preview:

1. Insert the fill picture to Pages.
2. Create a text box with the text you want. Use black text.
3. Copy the text box.
4. Open Preview and select File > New from Clipboard.
5. Save the image as jpeg (to get rid of the transparency of the background).
6. Copy the image from Preview.
7. Paste it into Pages.
8. Position the fill image behind the pasted picture.
9. Use Format > Instant Alpha to make the text transparent, and the image will be visible through it.

How do I change the default font?

If you are not happy with the default font in Pages' templates, you can correct it by changing the styles in the template and saving it. Then go to Preferences and select the changed template as default for new documents.

Why does the layout change when I import a Word document?

When you import (or export) a Word document, the layouts in Pages and MS Word are not identical. Some things do not simply transfer, as described here.

However, even when all present document features are supported in both programs, the layout may differ.

Text that fits on one page in one application may not do so in the other. Still, all the metrics is the same: font, font size, line spacing, character spacing, and so on.

If you look closely on the picture above, you will see that the characters have the same height in both applications, but the space between the lines is slightly off.

My guess is that this is for the historical reasons described in this article. MacOS and Windows calculate the line height in slightly different ways. MacOS uses the variables Ascender, Descender and LineGap, while most Windows applications use usWinAscent and usWinDescent. The variables mean almost the same thing, but not quite. There is more information in this article from Adobe.

MS Word needs to be 100% compatible with the layout of Word for Windows. It is MS Word, after all. And Pages clearly needs to use the MacOS way of doing things. The result is that the lines do not have exactly the same height.

Which font is that really?

You are writing a text in Pages, where one character is unusual. Let's say you have chosen Party LET as font, and you type the phrase 'In Romanian an apple is called “măr”.' Everything goes fine, until you type the Romanian word măr.



All the characters display fine in Party LET, but the ă looks very different. And yet you can see from the font Palette that it is the same font as the rest of the document. Pages knows that Party LET does not contain the character ă, and therefore uses another font, but which one?

You find the answer by pasting the text into TextEdit. If you highlight the ă in TextEdit and display the Font palette, you can tell that the font used to render the character is Lucida Grande.

Which fonts are included with iWork '09?

Unless you already have them installed, iWork '09 and iWork '08 will install the following fonts on your system:

• Academy Engraved LET
• Bank Gothic
• Blackmoor LET
• BlairMdITC TT-Medium
• Bodoni Ornaments ITC TT
• Bodoni SvtyTwo ITC TT
• Bodoni SvtyTwo OS ITC TT
• Bodoni SvtyTwo SC ITC TT
• Bordeaux Roman Bold LET
• Bradley Hand ITC TT-Bold
• Capitals
• Jazz LET
• Mona Lisa Solid ITC TT
• Palatino
• Party LET
• PortagoITC TT
• Princetown LET
• Santa Fe LET
• Savoye LET
• SchoolHouse Cursive B
• SchoolHouse Printed A
• Snell Roundhand
• Stone Sans ITC TT
• Synchro LET
• Type Embellishmnt One LET

The abbreviations here stand for:

• ITC - International Typeface Corporation
• LET - Letraset
• MD - Medium
• OS - Old Style (used for the kind of figures that sometimes go below the baseline)
• SC - Small Capitals
• SvtyTwo - 72. The Bodoni 72 fonts are designed after Giambattista Bodoni’s 72-point “Papale” font.
• TT - TrueType. Also see Apple's Developer Connection.

Note: Apple's website has lists of the fonts that come installed with Mac OS X 10.4 (Tiger) and Mac OS X 10.5 (Leopard)

Why are some glyphs missing in Pages?

Glyphs are variants of characters in a font. One example is "fi", which in some fonts may use special glyphs to look like "fi". (Increase the text size in your browser, if you cannot tell the difference.) Sometimes glyphs are used to make superscripts like ² instead of 2. Sometimes, but not always, what you achieve with a glyph could also be achieved with standard unicode characters.

In a standard MacOS X application, you access glyph variants like Ligatures and other variants from the Font Palette's Typography option.



Each font can contain a large number of glyph variants or no variants at all. You can see exactly which glyphs are available in a font using the Character Palette.



There are of course different ways of handling glyphs in different kinds of fonts. Adobe and Microsoft use mainly OpenType fonts. Apple uses mainly TrueType fonts. OpenType fonts mostly work in MacOS X, but there may be some glyphs that MacOS X does not support.




For example, if you have Adobe InDesign, you can see a section of "Ornaments" glyphs in the OpenType font Adobe Caslon Pro. The selected pointed hand in the picture above is actually a "P" - something you can tell by copying it and pasting it to another application. You can also see that the unicode for the hand is 0050, and that is upper case P.

You can also see that the GID (Glyph ID) in Adobe's InDesign is 642. However Apple's Character Palette gives it GID 523. Clearly, something strange is going on.

If you access the Typography Palette for Adobe Caslon Pro in TextEdit, you do not have any Ornaments section. However, you can still double click the glyph in the Character Palette and display it in TextEdit.

In Pages you cannot even add it by double clicking it in the Character Palette, when you are running Mac OS X 10.4.

And why? Well, because it is an unsupported feature. It may not be a very exhaustive explanation, but that all there is right now.