Pages - Save As...

In most applications, you can save an open file under a new file name with File > Save as... or shift-command-S.

In recent versions of Pages and TextEdit, the command is File > Duplicate > File (again!) > Save.

There is no keyboard shortcut for this, unless you customise your keyboard shortcuts in System Preferences > Keyboard > Keyboard Shortcuts > Application Shortcuts.

This admittedly makes Save as... more cumbersome to use, but it is a (somewhat) logical consequence of the Autosave feature of Pages, which is so automatic that you never should have to save a file again. Almost.

How do I unlearn words from the spelling dictionary?

Let's say that you write a text about someone with the incredibly attractive name "Magnus". The name is underlined in Pages as incorrectly spelt, if you type in English. To add the name to your spelling dictionary, you may simply right-click (ctrl-click) on it and select "Learn Spelling" from the menu, and Pages will from now on accept the spelling.

Now, assume that by mistake the word you right-clicked was "Nagnus". To tell Pages that you made a mistake that should be forgotten, you right-click the word and this time select "Unlearn Spelling" from the menu.



This technique applies to TextEdit as well.

In older versions of Apple's software, you could unlearn words from the Spelling dialogue box, but with current versions, the way to go is right-clicking.

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.

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 import and export text files in different encodings?

Pages does not pretend to be a text editor. If you want to edit text files, you are much better off using TextEdit or other programs.

When you Export a text file from Pages, it usually uses either Western (Mac OS Roman) or unicode UTF16 as encoding. You cannot choose which encoding you want, and you cannot for sure tell what encoding it was, unless you verify in some other program like TextWrangler.

When you import text files, Pages can usually open UTF16 without any problem and usually also Western (Mac OS Roman). Pages is unable to open the common UTF8 format.

The workaround is to always use TextEdit or another program for text files. You can then copy the content to Pages - if you want to.

How do I create my own Color Palette?

Sometimes you may want to use a limited number of colours for a document. Let's for example say that you want certain words in blue. If you use the standard Color Wheel in the color window (View > Show Colors), you may end up with slightly different shades of blue, depending on where you click.


To be sure that you always select the same colour, you can drag colours from the rectangle next to the magnifying glass to the strip at the bottom of the window.



The strip contains 15 squares by default, and that should be more than enough for most people. However, if you need more, you can drag the the dot below to make room for more squares.



You may need several sets of colours. Let's for example say that you want one particular set of three colours in one document but another set of three colours in another document. You can handle that as well in the Color window, using the third tab, called "Color Palettes".



Here you can choose between a few pre-defined palettes, like Apple, Web Safe Colors or Developer, but you can also create your own ones, clicking on the wheel, and choosing "New".



You can of course rename both the colours and the colour palettes to whatever names you like.




So, how do you select colours for your palettes? You can do this in (at least) two ways.

One is to click on the magnifying glass and then click on an area of the screen that has a colour you want to capture.



The other method is to select a colour using one of the other icons on the top. Then go back to the "Color palettes" icon.

After you have selected a colour, you drag it into the empty area of your palette or click on the + button. That's it. You do not even have to save, as the colour palette has auto-save (in contrast to Pages documents).

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.

Where did all those tabs come from?

When you open a Pages document, it has no visible tabulator stops at all.

However, there is a hidden set of default tab stops, just like in Open Office, Microsoft Word and many other word processors.

As soon as you add a manual tab stop to a paragraph, all previous default tabs disappear:


The distance between the hidden default tabs is defined in the inspector.



However, sometimes a paragraph suddenly gets plenty of visible tabs:

This can happen if you paste text from applications like TextEdit or AppleWorks. These applications do not have the concept of hidden default tabs, so they have to use real visible tabs instead.

The easiest way to get rid of them is to apply a paragraph style without tabs. You can often simply click on the red triangle to the right of the style name and choose "Revert to Defined Style".

How can I check grammar in a Pages document?

Pages 3.0 contains no "grammar check" but it contains a "Proofreader", which tests things like these for English texts:

• Improper capitalization (like a sentence starting with a lower case letter)
  
• Duplicate words
• Using "an" instead of "a"
• Full stop inside quotation marks ("He screamed". <> "He screamed.")
  
• Formatting errors (for example, abbreviations that should be spelled out in formal writing)
• Jargon
  
• Gender-specific expressions - like "mankind" instead of "humankind" or "humanity".
• Date format ("12/24/07" is considered too informal).
  

With Mac OS X 10.5 (Leopard) the OS got its own grammar checker, which is not used by Pages 3.0.1. It contains some checks for pure grammatical errors like:

• Verb conjugation ("I is". "I have did".)
• The difference between "their" and "there" (as in "there house").
  
• Sentence fragments (sentences without a verb - like this one).
  

To use the OS grammar check, paste the text into TextEdit and verify it there.

However, the OS grammar check does not check for the following issues, which Pages' Proofreader checks for:

• Inconsistent spacing or punctuation marks, like "la Arabie" for "l'Arabie" in French.
  
• Complex words like "eventuate" or jargon like "pretty".
• Gender words like "mankind".
• Date formats.
  

In some ways the lack of vocabulary check may actually be good, as you sometimes want to write for example "pretty", and Pages cannot switch off that check.

For grammar checks for other problems, try for example MS Word or Grammarian.

How do I make Pages autosave my documents?

With the new Mac OS X, Lion, released in July 2011, Pages '09 automatically saves all open documents using Auto Save and Versions. The basic functionality is very easy: open the document, edit, close. That's it. To use Versions and the more advanced functionality, it is a good idea to have a look at Apple's description of the functionality.

However, the autosave functionality is not problem free. There have been reports of people who have lost some data. The data is not autosaved continuously, but at regular intervals, and if you crash your machine between those intervals, text will obviously be lost.

For older versions, there was a problem, which is described below:

Pages '09 before Mac OS X Lion could not automatically save documents, so if you had typed for 5 hours without saving and there is a power failure, you would have lost all your work.

The safest way to handle this is to press ⌘-S to save the document manually as often as possible.

For those who do not trust themselves to remember this, there are a few Applescripts to do this at Apple's discussion forums, for example here and here.

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.

Why cannot Pages show pictures in .rtf files?

Part of the reason is that Pages is silly. If a picture is in a file, it should of course display it.

However, there is method in the madness. When it comes to rtf-files, Apple decided not to support pictures, as the rtf handling of images is too limited. Rtf supports only jpg pictures and png pictures and a number of "meta" image formats. This means that if you insert for example a small eps or pdf-file into an rtf document, MS Word will have to convert it to jpg or png, and then it is no longer scalable, even if you print on a printer with high resolution or with a large paper format. You can see this by simply increasing the view size in MS Word.

When an application like TextEdit saves to rtf, it instead uses rtfd, which allows for pdf and other high quality scalable formats.

If you open an rtfd from TextEdit in Pages the edges are still smooth with a high magnification. However, in any magnified rtf Word the edges of original PDF files are jagged.

So, Pages it not that silly after all? Oh, yes it is:

1. If a well formatted rtf file contains a picture, there is no excuse why Pages should not display it.
2. When Pages exports to rtf, it does not warn you that it is not going to export to rtf at all, but to rtfd, which no Windows application can read.
3. Not only that, the embedded picture in the rtfd file is not PDF! It is tiff, which is a rasterized bitmap format, so it still gets the jagged edges.

How well does export/import of MS Word documents work?

Before Pages '08, very few people complained about the import of MS Word documents to Pages.

However, when you export a complicated Pages document to MS Word you are likely to lose some formatting, and the layout will change to some degree.

Some features are not supported. Note that not all Word documents contain this kind of features.

• Pages does not support separate page orientation per page, so if you have a Word document where all pages except one have portrait orientation, there will be no difference in Pages. Pages will use the page orientation defined for the first section in the document.
• Pages does not support text frames.
• Pages does not display the full content of table cells that span several pages.
• Word macros will not work.
• Partial paragraph borders will be simplified. All borders except complete outside borders will be removed.
• Italics and bold of fonts without italic and bold typefaces will be lost.
  
• Asiatic vertical text orientation and furigana/ruby/phonetic guides will also be lost.
• And so on...
  

With Pages 3.0 came the possibility to import .docx files from MS Office 2007. At the same time, there seems to be an increased number of complaints about MS Office compatibility in general. It is unclear if this is because the compatibility has become worse, or if more people have started using Pages for Word documents.

The standard Word format version we have come to expect Pages to support is the one used by Word 97 through Word 2003 for Windows, and versions from Word 98 to Word 2004 for Mac. (Internal numbers are Word 8 to Word 11.)

Pages '08 cannot open Word 6.0 or Word 95 formats or earlier. NeoOffice can open them and save to newer versions of Word, which Pages then can read. Even TextEdit can open them but almost all formatting will be lost.

One may note that even MS Word for Windows is not fully backward compatible with itself without a registry update.


A Pages document that almost was saved as a Word document.