When you choose fonts for Office, it takes a different approach than selecting typefaces for an InDesign document. One obvious difference is that you only need to install the font for a design document on the computer where it’s being created. Using the same font in an Office program will require the font to be installed on every computer using the document. Clearly, this is a much more costly solution. Aside from that, let’s look at the pitfalls of choosing fonts for Office templates.
Choosing Fonts for Office – Designer Vanity
Designers from different geographic areas spec fonts differently. As one example, Toronto designers tend to focus on the practicalities of electronic document distribution. As a result, they will often choose Arial or Times New Roman for the user-filled portion of a template. By contrast, designers from New York focus on creating a distinct visual appearance. They choose unusual designer fonts. This creates logistical problems for their clients. They must spend money licensing for all workstations and then take time to install the fonts for each user.
Test fonts from small foundries to licensing a lot of copies. I’ve written about this issue before: Cross-platform Fonts from Small Foundries: Beware! In a mixed Windows/OS X environment, a poor quality font will not display correctly in documents that move between Mac and PC. One typical symptom is Italic text that displays as Roman or Bold when viewed on a different OS, or some similar weight/style mixup.
Choosing Fonts for Office – Collaboration
If the client uses Office documents for collaboration (Don’t know? You should be asking these questions!), you should seriously reconsider a “designer-y” font choice. When the documents arrive at your client’s client, that computer will not have the fonts and the document appearance will change drastically. Unlike web pages, Office documents do not have a font fallback setting. There is no practical way to preset which font will be substituted when the original is missing.
I know what you’re going to say next: “What about if we embed the fonts?” Here’s are several reasons why that probably will not work.
- Embedding only works with TrueType and TrueType-flavored OpenType. But you shouldn’t be using PostScript or PostScript-flavored OpenType for Office anyway. Microsoft’s support for that format is going away.
- Embedding doesn’t work at all in Office for Mac. OS X users cannot embed fonts in documents. Neither can they see the correct fonts in documents where the font is already embedded.
- Most typefaces have restrictive embedding permissions. So even if you can embed the font and your client can see it, they will not be able to edit the document using the embedded font. You can get around this if you contact the foundry and request a version with Editable or Installable permissions. Expect to pay a surcharge for this. Some foundries charge a lot for this service, because they’re concerned about losing sales to possible piracy.
Choosing Fonts for Office – Font Families
Designers are used to Single versions of fonts. The is where each font variant appears as a separate entry in the font list in Office. If you want to change to bold or italic, you select a different font from the list. Office doesn’t usually work this way and Office users are not used to this method.
When all four faces in a font family are installed, using the bold and italic buttons has the intended effect of switching fonts.
Instead, Office users are familiar with Family fonts. This is where where a group of (usually 4) fonts is linked. To get bold or Italic variants, they click on the Bold or Italic buttons, leaving the font name the same. The foundry usually creates the font families, though there are some type utilities available that let you make a family out of single fonts. RoboFont is one that works. Some other popular utilities do not do this correctly. Use them and you’ll end up with a family that only works on Windows or OS X, but not both.
If the font is not set up as a family-style font, then using the bold and italic buttons fakes the look with stroking and/or slanting the roman. The result is a disastrous visual effect.
In OS X, it’s not obvious when you are using single versus family fonts. OS X creates family groupings on the fly. In Windows, it’s easy: install the fonts, then look at the font menu in an Office program. A font family will only have one entry for the family, while singles will list every font variant. In this screen shot, the Arials are families. Arnhem and ATC Arquette are collections of single fonts:
The Arials are families, while Arnhem and ATC Arquette are singles.
The logical conclusion to the font family approach is that your client should almost never be licensing just one or two typefaces. If four family members are not installed, Office will fake them by stroking the font for bold and slanting it for italic. As you might guess, this looks ghastly and completely off-brand.
The exceptions to this rule are:
- If the document is a fillable form in Word or Excel. Those documents are typically locked so the user can’t change the font or its attributes.
- The the font is used only for Headings. These are usually bold and stay that way, so there is less chance of a user applying attributes.
In either of these 2 situations, you should be able to get away with licensing a single typeface instead of a complete family.
A font family with all 4 members installed. The bold and italic button work as expected.
Here is a family-style font with only the Roman installed. Using the bold or italic buttons gets you this dreadful look, plus an out-of-memory warning from Office.
If your design calls for an unusual mix of weights, like Light and Demibold instead of Regular and Bold, contact the foundry to request a custom family. There is normally a small charge for this service. However, if the licensing deal is large enough, the foundry may waive this.
Choosing Fonts for Office – 2 Solutions
To sum up, for each different font used in your design, your client should be licensing a complete family of 4 typefaces in TrueType or Truetype-flavored OpenType.
Brandwares is a font reseller and we’ve been speccing type for Office for years. If you choose us to create your templates, we can also source your client fonts in the correct format and family. This service includes free tech support. We’ll help your client with any installation or usage issues and communicate with the foundry, if necessary.
Working on your own? A simple way to eliminate all these issues is to design with the fonts that are already installed by Office. There are many faces more interesting than Arial and Times New Roman in this collection. The fonts that come with Office don’t require any additional licensing fee. They are already installed and they have relaxed embedding permissions to make collaboration easy. They are all high-quality typefaces licensed from major foundries like Monotype. Here is a list of the families that are useful for business communications (we left out Comic Sans!). For maximum compatibility among all versions of Office, use a font that is checked in every column.
Click to open PDF
It’s a challenge to create the absolute best quality logos for client files in Microsoft Office. Most artists choose bitmap formats for logos, usually JPEG format. Apparently this is some kind of received wisdom from artist to artist, because JPEG format is close to the worst possible format for logos. But I’ve already covered this subject in JPEG Logos? Fail! back in 2013.
Brandwares has used indexed-color PNG format for most line art (a term for non-photographic art that is mostly flat color areas). Most logos qualify as line art. But there are a couple of disadvantages to using any type of bitmap format for branding information.
With Office files, Microsoft is determined to foist image “compression” on us. I put compression in quotes because Microsoft’s solution is really downsampling by another name. Whatever the name, the results are blurry and absolutely do not reinforce the brand. All bitmap files will be downsampled unless the user chooses only a single file. You can’t protect the company logo, even with XML hacking. Let’s face it, sooner or later, bitmap logos will look like mush.
The other persistent problem with bitmap formats is what happens when you create a PDF from a document. Acrobat’s default settings assume you want to create a small file to post on a web page. This was a serious problem 20 years ago. So, once again, a software company’s helpful authoritarianism leads to default settings that cream the logos in any Office file.
Vector Formats for Best Quality Logos
For many years, we at Brandwares were aware that a vector format was a potential way out of this. Vector formats are naturals for line art, because they easily handle geometric shapes with simple coloring. But there are relatively few vector formats from which to choose, and the available formats didn’t seem up to the job.
One grandaddy of vector formats is the EPS file. Well-known to designers, the EPS doesn’t get great support in Office programs. Printing them at high resolution requires PostScript support from the printer, which is dicey in most business offices. Office programs can’t ungroup them, so adding theme color support in an Office file is out of the question.
CGM was an early contender, and is still used in technical applications. But it never got support in common file formats. SVG is making inroads on the web, but Office is only beginning to support the format.
Let’s be honest, Microsoft offers the best support to the formats it invents. For vector graphics, that is WMF and EMF. WMF is a 16-bit format that was invented in the ’90s. In practice, it’s not too useful today. All too often, WMF files do not render the inside curve of shapes like O or D. In addition, Adobe Illustrator’s WMF export is horrendous, turning every curve into a series of angled straight lines. Corel Draw does a better export, but the format is limited by its 16-bit capacity.
The format we’re left with is EMF (Enhanced MetaFile). We’ve tried EMFs exported by Illustrator, but they aren’t so great. Illustrator’s curve accuracy goes down the toilet when it exports as EMF, even though it puts Corel Draw to shame. But at this point, we realized that there might be other programs that could do a better job with EMFs.
And there is! Forget Illustrator, forget Corel Draw! For now, the king of the EMF planet is the freeware program Inkscape! This open source vector illustration package creates top-notch EMF (and SVG) graphics and can import Illustrator AI and EPS graphic files. InkScape features much better curve accuracy than Illustrator can export. Here’s the complete workflow to create a robust logo that is a small file size and sharp at any resolution and has a transparent background and will never get downsampled by Office or Acrobat!
Best Quality Logos, Step-by-Step:
You’ll need a piece of artwork in Adobe Illustrator (.ai) or Illustrator EPS (.eps) to try this out. You can download Inkscape for OS X or for Windows.
- In Illustrator, open the .ai or .eps file and choose the Selection tool (dark arrow). Click on the logo. If the logo outlines are selected when you do this, go to step 3. However, if clicking on the logo activates a rectangle around the logo, proceed to step 2.
- The rectangle that gets selected is a clipping mask and/or a compound path boundary. In Illustrator, choose Object>Clipping Path>Release. You might have to do this several times, until all clipping masks are removed. Select the rectangles. If part of the logo also gets selected when you choose a rectangle, you’re not done. When you can select just the boundary rectangles, delete them. If you neglect this step, PowerPoint can resize the clipping mask which makes the logo look cropped.
Depending on the logo, you may also need to release the Compound Paths on the same menu. Doing this will cause the inside of A, O, D, etc. to fill in. If this happens select the paths for letter outline and the inside and choose Object>Compound Path>Make. Compound paths don’t cause problems around single letters, but they may cause issues around large groups of shapes.
- Save the file and close Illustrator.
- Open the file in InkScape. (Inkscape prefers more recent formats of .ai. If you see an import error message, try saving the file in Illustrator to a newer format)
- Choose File>Document Properties.
- On the Page tab of the dialog, expand the line Resize page to content by clicking on the plus sign.
- Change the units dropdown to in (inches)
- Set each of the 4 margin fields to 0.01 to add 1/100″ to the logo area.
- Click on Resize page to drawing or selection, then close the dialog.
- Choose File>Save As… and set Save as type: to Enhanced Metafile (*.emf). Save the file and close InkScape.
- Open PowerPoint, choose Insert>Picture and place the logo file. If it is the correct color you’re done. However, if you need to key part of the logo to the presentation theme, or if you need transparency in part of the logo, continue with the next step.
- With the logo selected, choose Picture Tools>Group>Ungroup. PowerPoint will pop up a notice: This is an imported picture, not a group. Do you want to convert it to a Microsoft Office drawing object? Click on Yes
- Once again, choose Drawing Tools>Group>Ungroup. Yes, you have to do it twice! This time, the drawing is actually ungrouped.
Best Quality Logos Extended
Once the file is ungrouped, you can key part or all of it to a theme color. If your presentation contains multiple color themes, then changing themes will change the keyed logo element automatically. This can be a slick trick for presentations with different sections in different code colors.
The layout for these slides is identical. Each uses a different color theme that varies one code color.
Transparency is not supported in most EMF exports, but by importing and ungrouping the logo, you can add transparency back in. In PowerPoint, choose Drawing Tools>Shape Fill>More Fill Colors…, then set the Transparency slider. This works the other way around from Illustrator, but the units are the same. If the Illustrator file used 40% Opacity, set 60% Transparency in PowerPoint.
From L to R: each character has 10% more transparency. You can’t get this by adding transparency in Illustrator, you must re-create it in Office.
EMF are not a great candidate for objects like disclaimers. Each letter includes one or 2 complex curves, so a paragraph of text will be much larger that the same disclaimer rendered as an indexed-color PNG or even a JPEG of the same text. But for logos, they’re pretty great. You get the same small file size and pin-sharp appearance regardless of how much you enlarge it. Applying image compression or printing to a low-res PDF leaves EMF logos in pristine condition. It’s by far easiest way to create the best quality logos for Microsoft Office.
I wrote about how to create a basic font theme in 2015: XML Hacking: Font Themes. Thanks to everyone for the comments and feedback that have allowed me to refine the article and make it more helpful.
That article covered a bare bones font theme for European languages (referred to as Latin fonts in Microsoft-speak). International and multilingual users require a theme that can work with a greater variety of languages and fonts, so in this article I’m going to cover how these work and how to create them.
A More Complete Simple Theme
There’s more we can do with the very basic theme from the previous article. In the listing below, a font has been specced for only Latin fonts.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<a:fontScheme xmlns:a="http://schemas.openxmlformats.org/drawingml/2006/main" name="Test">
In both the Major (Headings) and Minor (Body) categories, there are also ea (East Asian) and cs (Complex Scripts) entries. These theme entries are inactive until text is formatted as a relevant language. As long as your text is marked as US English (either by using the Review>Language>Set Proofing Language, or by setting the language in a Style), only the Latin theme fonts will be active. But if you mark text as Chinese, the Office program will check the theme and use the font in the ea tag instead. Likewise, Persian text will activate the cs theme font.
What will not work is to try to set an East Asian or Complex Scripts font in the Latin tag. Depending on the version and platform of Office, you’ll only get European characters showing, or the program will completely ignore your theme. Here’s a simple font theme that will work with Japanese, Arabic and European languages:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<a:fontScheme xmlns:a="http://schemas.openxmlformats.org/drawingml/2006/main" name="Test">
Depending on which ea or cs font you choose, it may support one or several languages. As an example, CJK fonts will support Chinese, Japanese and Korean. Of course, in a collaboration scenario, the fonts chosen should be available on both Mac and Windows, or the display of one of the langauges may get mangled with a font substitution. The best idea is to stick with fonts distributed by Microsoft with Office.
Complex Font Themes
When you crack open the XML on a document or theme, the font theme information is contained in theme/theme1.xml. This illustrates a font theme that is ready to take on the world:
<a:fontScheme name="Office Theme">
<a:latin typeface="Calibri Light" panose="020F0302020204030204"/>
<a:font script="Jpan" typeface="ＭＳ Ｐゴシック"/>
<a:font script="Hang" typeface="맑은 고딕"/>
<a:font script="Hans" typeface="宋体"/>
<a:font script="Hant" typeface="新細明體"/>
<a:font script="Arab" typeface="Times New Roman"/>
<a:font script="Hebr" typeface="Times New Roman"/>
<a:font script="Thai" typeface="Angsana New"/>
<a:font script="Ethi" typeface="Nyala"/>
<a:font script="Beng" typeface="Vrinda"/>
<a:font script="Gujr" typeface="Shruti"/>
<a:font script="Khmr" typeface="MoolBoran"/>
<a:font script="Knda" typeface="Tunga"/>
<a:font script="Guru" typeface="Raavi"/>
<a:font script="Cans" typeface="Euphemia"/>
<a:font script="Cher" typeface="Plantagenet Cherokee"/>
<a:font script="Yiii" typeface="Microsoft Yi Baiti"/>
<a:font script="Tibt" typeface="Microsoft Himalaya"/>
<a:font script="Thaa" typeface="MV Boli"/>
<a:font script="Deva" typeface="Mangal"/>
<a:font script="Telu" typeface="Gautami"/>
<a:font script="Taml" typeface="Latha"/>
<a:font script="Syrc" typeface="Estrangelo Edessa"/>
<a:font script="Orya" typeface="Kalinga"/>
<a:font script="Mlym" typeface="Kartika"/>
<a:font script="Laoo" typeface="DokChampa"/>
<a:font script="Sinh" typeface="Iskoola Pota"/>
<a:font script="Mong" typeface="Mongolian Baiti"/>
<a:font script="Viet" typeface="Times New Roman"/>
<a:font script="Uigh" typeface="Microsoft Uighur"/>
<a:font script="Geor" typeface="Sylfaen"/>
For brevity, I’ve omitted the Minor font section. Instead of setting the ea and cs fonts, this font theme has entries for more tightly defined language groups and different fonts assigned to each one. This level is detail is necessary for a font theme that can be used around the world. Since I copied this listing from theme1.xml, it doesn’t have the XML opening that a standalone font theme would have.
Setting up and testing a complex font theme like this is not a simple task. The font switching is automatic and is triggered by the language input setting on your computer, the language set in your template styles and the language set in the text being edited. Please post your comments, let me know of any hiccups or problems you notice and I’ll try to answer your questions.
Recently I was creating a white paper template in Word for a client and needed to insert some custom Picture Content Controls for photos that would be inserted by users. The designer had specced round-cornered pictures, but Picture Content Controls (PCC) have square corners. It didn’t take long to figure out that after selecting the PCC, I could choose the Picture Tools>Format tab of the Ribbon, then apply a Picture Style. I chose the rounded corners with reflection (fifth icon over in Word 2010), then removed the reflection.
Now I had rounded corners, but also another problem. Word keeps the corner radius in proportion to the box size, so resizing the PCC up to the right size made the radius much larger than the design. Unlike AutoShapes, Content Controls will not display a yellow radius handle to adjust the radius. I also tried resizing the PCC before applying the Picture Style, but got the same big corners.
A Picture Content Control with default corner radius.
Custom Picture Content Controls XML
When I’m stuck, I crack open the XML. Can’t leave it alone! If you’ve never opened Office files to edit their XML, read XML Hacking: An Introduction. If you’re using a Mac, you should also read XML Hacking: Editing in OS X. All document content is in word\document.xml, so I opened it and started searching. In some respects, a PCC is handled like an ordinary picture, so I found it inside a <w:drawing> tag. The information I was looking for was in this subsection:
<a:off x="0" y="0"/>
<a:ext cx="3222172" cy="4576355"/>
<a:gd name="adj" fmla="val 8594"/>
When I spotted the line <a:prstGeom prst=”roundRect”>, i was pretty sure that’s what I was looking for. But inside that tag, there were only 2 parameters. I went for the fmla tag and change the value from “val 8594” to “val 4000”. Because I’m experimenting, I make only 1 change, then zip the XML to test. If you make several changes and the file doesn’t open, it can take a long time to find the error.
I reopened the Word file. Success! The corner radii were about half the size. Then I just had to try several values until I found one that match the designer’s intent. Keep in mind that the fmla value is not setting any particular radius size, it’s setting the ratio of the curve to the size of the picture. So you should make the placeholders the correct size first, then try out fmla values to get the radius you want at those dimensions.
You don’t always get lucky with parameters. A few lines down I spied another setting that looked like it could be useful. While you can set the PCC border in the program interface, you can’t set the fill color. However, in the XML, I saw these tags:
Unfortunately, changing these values had no effect on the color of the Content Control. So what do these tags do? Search me, maybe someone at Microsoft knows. But I was happy to be able to set the radii to my preference. Here’s the final result:
A custom Picture Content Control with smaller corner radii.
In my last post, I translated the classic method of outline numbering for OS X. But Shauna Kelly’s original steps have an element of personal preference them. We can also get reliable results from outline numbering variations.
Unfortunately, Shauna passed away a few years ago. I’m glad her site is still kept running by volunteers. If you’re formatting for Windows, you should read her article first: How to create numbered headings or outline numbering in Word 2007 and Word 2010
I think one notable restriction of Shauna’s procedure is that she relies on the built-in Heading styles. Often a numbering scheme is required that has nothing to do with headings. Here’s how we can separate these concepts and create solid numbering using an arbitrary style set. This applies to both Windows and OS X versions of Word.
Outline Numbering Variation – Alternative Styles
In Shauna’s classic technique, the first step is to revise the built-in Headings 1 to 9 so that Heading 1 is independent of other styles, then all the subsequent headings inherit characteristics from Heading 1. We’ll reuse this basic concept for a different style set.
First create a style that will be the basis for the first level of your outline numbering. For a start, this style should be based on No Style (Word OSX: Format>Style>Modify>Style based on:>(no style) Word for Windows: Ctrl + Alt + Shift + S to open the Styles list>Click on Manage Styles button>Modify>Style based on:>(no style)). This style really only needs to include the font, font size, line spacing, space before and after the paragraph. Any indenting or number style will be handled later. For this article, let’s call it Number Style 1. There is one essential parameter you must set. In the Paragraph format for the style, you must set the Outline level to Level 1 (With the Modify Style dialog still open, click on Format>Paragraph>Outline level. This is the key to making this work!
Next, we’ll create the second style. Start by basing it on Number Style 1, then format whatever variation it might have, staying away from indentation or numbering. Outline numbered styles are often very similar, this style might be exactly the same as Number Style 1. However, in Format>Paragraph, Outline level must be set to Level 2. Are we picking up the pattern yet?
Each additional style in the outline numbered series must be:
- based on the previous style, and
- have an outline level that is one level down from the previous style.
As long as you can format a chain of styles following these principles, you should be able to get it to work with the technique on this page for OS X (replace the first section Outline Numbering in Word for OS X – The Classic Method with the procedure on this page) or Windows (replace section 3. Set up your Heading paragraph styles with this page’s technique instead.
Outline Numbering Variation – Nested Bullet Styles
You can create nested sets of bullet styles by following the same steps as above. When the Define new Multilevel list dialog is open, use the dropdown called Number style for this level, scroll all the way down and you’ll find 6 bullet presets and options for choosing a different bullet or a picture bullet. Nested bullet styles work like outline numbering for bullets, though they’re a new concept for most users.
Feel free to post constructive comments suggesting improvements, I’m always trying to make these articles better.
Unlike most of my articles, this one is not a piece of original research. Shauna Kelly wrote the definitive method for producing outline numbering in Word several years ago. Unlike most of what you’ll read about techniques for creating numbering in Word, Shauna’s procedures actually work reliably. Unfortunately, Ms. Kelly passed away several years ago, though her web site has been kept going by volunteers. You can read her original posts here: How to create numbered headings or outline numbering in Word 2007 and Word 2010. My contribution is to document the steps needed to produce outline numbering in Word for OS X.
The names of some commands are different, or they’re found in a different place. I’m sticking to the step-by-step approach. For an in-depth explanation of why the steps work, please consult Shauna’s original pages. These instructions are quite specific. Please don’t include any steps not on the list below, or you’re on your own for the results.
Shauna argued strongly for using the built-in heading styles Headings 1 through 9. There’s nothing wrong with this and it can save a few steps. Sometimes, however, I prefer to save heading styles for headings and create a separate set of styles for numbering. In this article, I’ll translate Shauna’s classic method. A future post will show some optional variations. If this is to be the basis for future documents, you want to be making these changes in a template. If you do this in a document and don’t apply the changes to the source template, you’ll have to redo all these steps for the next document.
Outline Numbering in Word for OS X – The Classic Method
- Choose Format>Style and select Heading 1. (If you’re not already using Heading 1 in your document, change the List: dropdown to All styles)
- Click on the Modify… button.
- Change the Style based on: dropdown from Normal to (no style) at the top of the list, then click on OK. While the dialog is open, choose Format..>Paragraph and set the Left indent to 0 and the Special indent to (none). If there is any indenting, these will be set later. If you had already formatted Heading 1, you may need to make some changes after detaching it from Normal.
- Select Heading 2, click on Modify… and change Style based on: to Heading 1. OK out.
- Repeat step 3 for each built-in Heading style, for as many levels of outline numbering as you require. Each style should be based on the one before.
Opening the Right Dialog Box
- In the Paragraph section of the Home tab, choose Multilevel List>Define New List Style. Avoid starting from Numbered List, that is not reliable.
Multilevel List>Define New List Style in Word 2011 and 2016
- In the Define New List Style dialog, give your style a plural name like Headings or Numberings, since this will apply to several styles.
- Click on the Format button and choose Numbering…
Set the style name and click on Format>Numbering (Left: 2011 Right: 2016).
- Now the Bullets and Numbering dialog opens, an extra step that doesn’t happen in Word for Windows. Click on the Customize button.
Link a Paragraph Style to a List Style
- Finally we get to the Customize Outline Numbered List dialog. Once this dialog is open, we will leave it open until all levels are set up. Start by clicking on the dialog expander button to see all the options (circled in red):
Top: Word 2011 Bottom: Word 2016 for Mac
- Now we start a sequence that will be repeated for all the outline levels to be formatted. First we attached the paragraph style to the list style. Start by selecting 1 in the Level list.
- Now select Heading 1 in the Link level to style dropdown:
Top: Word 2011 Bottom: Word 2016 for Mac
Set the Numbering for the Style
- In the Enter formatting for number: field, you can delete any content displayed. If the first outline numbering level starts with text, like Chapter 1 or Section 1, type in the text and a space.
- Using the Number style for this level: dropdown, choose the number appearance. A number appears in the Enter formatting for number: field.
- Add any punctuation or symbol that is to follow the number.
Repeat for All Levels
- Repeat the steps above for all levels to be formatted. Select 2 from the Level list, Heading 2 from the Link level to style: dropdown, enter text and select a number style.
- On lower levels, you often want to include numbering from a higher level, so level 2 may appear as 1.1. You can do this by clicking in the Enter formatting for number: box where you want the previous level to appear, then choosing a level from the Include level number from dropdown.
Outline Numbering in Word for OS X has a quirk: the Level 1 choice is already displayed, even if no number appears in the Enter formatting for number: box. Just click on the dropdown and re-select the Level 1 that already appears selected and Word will do the right thing.
Set the Indentation for all Styles
Set the number position, tab and indent for each level. Left alignment for numbers is most common, but Roman numerals can look better right-aligned, since their width varies more. Normally the tab and indent are set for the same amount. The tab controls the position of the first line and the indent all the lines in the paragraph after that.
Editing Outline Numbering in Word for OS X
Like every good designer, you’ll probably want to tweak these styles later. For paragraph styling, like the amount of space before or after, you can simply modify the paragraph parameters. That’s easy. But anything to do with the numbering or its positioning relative to the paragraph should be done in the Outline Numbering dialog. Unfortunately, both Word 2011 and 2016 have a bug that makes it impossible to edit an existing List Style.
- In the Quick Style Gallery, right-click on Heading 1 and choose Modify Style.
- Click on the Format button and choose Numbering. The Bullets and Numbering dialog opens to the List Styles tab, where you can’t modify, add or delete anything: the buttons are permanently disabled. Serious bug!
- Click on the Outline Numbered tab. None is highlighted, which is not helpful. Examine the tiles carefully, you have to choose the correct one. Click on it and then on the Customize button. This will only work if you are editing the outline numbering on the same installation of Word on which you originally created it. Open in a different installation or version and the Bullets and Numbering tiles do not show your custom list.
- Edit the numbering, then exit when you are finished. Instead of editing your named List Style, Word has created a new list style autonamed Current List1. If you’re using a different installation of the program than what you created the list on, you can’t even use the Outline Numbered tab. All the tiles will display the stock numberings. Instead of editing your list style, you must start all over and get it right in one editing pass.
Word bug: the plus, minus and Modify buttons are permanently disabled.
Outline Numbering in Word for OS X: The Customize Outline Numbered list Dialog
Word is found everywhere, but Word users with training are a scarce commodity. It’s a shame, because a little training can go a long way to get really nice results. This article will cover the most common formatting mistakes that Word users make. If you’re a designer, you could still benefit, I see plenty of these errors from design companies as well.
Formatting Mistake #1: Not making the Non-printing Characters Visible
By default Word is set up to show “pretty” documents. Microsoft has decided that users want to see what the printed output will look like on-screen. So Word hides all the control characters that are vital for reliable formatting. Users can’t see the hidden formatting that they are inserting or deleting. Result: formatting mistakes! The only way you can provide professional documents for clients is by making these visible so you can deal with them. When you want to see the printed result, do a Print Preview. It’s fast and more accurate than the “pretty” screen display.
The exact steps for show the control characters is slightly different for each version of Word, so I’m not going to list them all here. To start in OS X, look for Word>Preferences>View, in Windows, choose File>Options>Display. Make all the non-printing or formatting characters visible. It’s also helpful to display Bookmarks, Object anchors and in Word 2010/2011 or earlier, Text Boundaries. In Windows, these last three are found on the Advanced tab of Options.
Now you can see Paragraph Marks, which hold the paragraph formatting for the text that precedes it. You can see the Section Breaks that hold all the header/footer, margins and page orientation information for the paragraphs preceding it. And you can see the Anchors for text boxes and floating pictures, which makes it much easier to anchor to a paragraph that is likely to stay on the same page.
Formatting Mistake #2: Creating New Pages with Multiple Carriage Returns
This is the classic hallmark of the Word user who has never taken a course or cracked a book. At the end of a topic, they’ll type enough carriage returns to get to the next page, then type a new heading. It looks perfectly fine on the original computer:
How it looks on your computer.
But then it’s sent to a different computer with different fonts or a different printer. The heading that supposed to be at the top of a page either moves to the bottom of the preceding page, or moves down so it’s not at the top of the page anymore. It doesn’t matter much which one happens, because the formatting mistakes scream Amateur Hour:
How it looks on a different computer.
Text flow in Word depends heavily on the font being used and the printer that has been selected. If you move the document to a different computer, they might not have the same font. Even a change in the version of a font is enough to make the text break differently. As for the printer, Word fabricates pages on the fly by using the metrics of the selected printer. These metrics come from the printer driver. So if the user who receives the documents has a different printer, or even a different driver for the same printer, the pages will be laid out differently.
The knowledgeable Word worker will insert a Page Break (not a Section Break) at the end of a text block to create a new page:
Page break: How it looks on every computer.
A really clever user will create a heading style that includes the paragraph attribute Page break before, so that whenever the heading style is applied to text, it automatically pops to the top of a new page:
Heading Style using Page Break Before Setting
Formatting Mistake #3: Using Tabs to Arrange Data in a Grid or Table
Whenever you need to arrange comparative information in rows and columns, you’re creating tabular arrangement. It’s always a good idea to pause for a moment and really look at the kind of data you want to present, so that you can choose the best format for that. If you find yourself using tabs and spaces to create a grid of data, STOP.
Making a lame table with tabs and spaces.
Information in a grid is tabular data (from which the tab key takes its name), but tabular data should go in a table. That’s what they’re for! Tab keys are left over from typewriters, when there was no other way to create a data grid. Designers are also guilty of creating grids with tabs, because table tools are relative newcomers to page layout software.
Use a table to arrange tabular information.
Tables are also the only professional way to make forms, which brings us to our next common mistake:
Formatting Mistake #4: Using Typewriter Techniques to Make Forms
Word, especially Windows versions, is loaded with excellent form-creation tools. But you’d never know it from the forms I almost invariably see created in that program. The common approach is to type a text heading, then dozens of underscores to indicate where the form-filler is to enter their data. This could pass for forms that are printed out and filled with a a pencil. You know, like people used to do 50 years ago:
Open the Word “form” on your computer and try filling it in. As you type, the underscores remain, trailing after your text. Type a couple of line of text: the left side of the filled portion falls underneath the heading, not to its right. The professional term for this is “a dog’s breakfast”.
The form falls apart when filled.
For forms that are filled on a computer, you need a much more robust method. Create a table with a cell for the heading and a separate cell for the filled-in area. If the form will only be filled out on the computer, you don’t need any horizontal rules to guide your text. The computer does that for you. If the form is intended to be dual purpose computer or hand-filled, add a thin border to the bottom of the filled-in cell. No other border are necessary or desirable. All of a sudden you have a form that is neat before and after filling, easy to read, even, dare we say, good-looking!
The right way to make a form: with a table.
Here’s a comparison of a table form and a typewriter-style form when filled with longer text:
Inserting long text
Formatting Mistake #5: Local Formatting Instead of Styles
Another giveaway of the Word amateur is when you click on different types of text and heading, but the Style always says Normal. This means the creator of the document made no use of Styles. Perhaps they think they are saving time, but the opposite is true. Repurposing or updating an unstyled document takes almost as long as creating it in the first place. Plus, useful Word features like a Table of Contents or the Navigation Pane don’t work well without using styles.
Using local formatting to imitate true styles.
After taking just a few minutes to create some basic styles everything about document creation and revisions is much faster. Styles are a true productivity booster. If you’re not using them, either you are wasting a lot of time, or you’re making someone else fritter away hours of their work day. Styles ensure your documents have a consistent, professional appearance. Updating their appearance in the future takes only a few minutes. It’s what the pros do!
A Heading Style applied.
You have a crucial thesis or presentation that’s due in the morning, but when you try to open it, you get a message saying the file has an error. It may seem like the end of the road, but with a little XML hacking, you can repair your file in just a few minutes and be back to work. Document repair is something you can do yourself.
First, let’s look at different causes of file corruption. The number one cause is working on files while they are on temporary or removable media. A USB or flash drive is a convenient way to carry data. The common alternative is to keep your information in the Cloud. But both of these are hazardous if you’re editing files. Accidentally ejecting a USB stick or losing your Internet connection while a file is open in Office is a near-guarantee of corruption. This type of corruption is also disastrous, because the file contents are so thoroughly scrambled, there is no way to recover the data.
But there are also files that get scrambled by software and usually these are recoverable. We’ll use the same techniques covered in previous posts. Windows users should review XML Hacking: An Introduction, while OS X hackers need to follow these instructions: XML Hacking: Editing in OS X
Is the File Recoverable?
When opened in Office, unrecoverable files may give you errors like these:
The first step is to rename a copy of the file with a .zip ending and expand it. An unrecoverable file (one scrambled by a USB or Cloud drive) will almost always raise an Zip error. Cut your losses, you’re not going to be able to fix this. As a second-best alternative, try opening the original damaged file in NotePad (on Windows) or Text Edit (OS X) to recover whatever text you can. You also might be able to extract some contents by opening in a different word processor, like Pages on a Mac.
By contrast, if you see the following messages, document repair is possible:
You can see that the first 2 messages are generic, while the second 2 give a specific location for the error. This means the file is at least partially readable by the program.
There are quite a few document repair articles on the web that are worth reading for the variety of tools that people are using. I prefer a combination of a good text editor (NotePad++ on Windows, BBEdit on OS X), plus a modern browser like FireFox or Chrome. The text editor is where you do the editing, while the browser parses the XML and finds any errors.
You’ve already unzipped the document or presentation, now look for the XML portion that contains the error. Most of the time, with a Word file, document.xml will be the culprit. Open document.xml in the text editor and Prettify (NotePad++) or Tidy (BBEdit) it to make it readable. A raw document.xml file only has 2 lines, which is why the XML errors are invariably reported as being on line 2. Making the text readable also adds useful line numbers to error reports, making the errors much quicker to find. Now the file should look like this:
Save document.xml, then open it in your choice of browser. This is how FireFox and Chrome show where the first error is:
As you can see, the report is a little more informative in FireFox. The error is a mismatched tag: a tag was opened but not closed. It expected to see the closing tag </mc:Fallback> and it tells you exactly where it thought that tag should be. The arrow points to the first character that is in error. The correct way to interpret this is that the expected end tag should be inserted immediately before the tag pointed to.
Document Repair Technique
Here’s what the error location looks like in the text editor:
Then here is what it looks like after inserting the closing tag (you can copy and paste directly from the browser window):
Save document.xml in the text editor, then refresh the browser. The next error is shown:
Repeat the steps. Some files have only a couple of errors, others may have dozens. You’ll know when you’re done, because refreshing the browser will give you a different screen, displaying the XML instead of an error message:
Rebuild the File
Close the text editor and browser, then re-zip the folders and [Content_Types].xml, giving the zip file a new name and a file ending that matches the original. Open it to ensure it works. Office does not tolerate XML errors well and doesn’t give you clear error messages, so if the file doesn’t open, you missed something. In addition, Mac users have to use Terminal to zip and view files, as noted on the XML Hacking: Editing in OS X page.
Lots of people ask “How can I prevent this?”, but there isn’t a really good answer. If a file can be repaired, it’s almost always due to a program bug that writes malformed XML. In the Word file used for example, this is often when a placed graphic has no fallback information, which is supposed to help with graphic depiction in older file formats. It appears that the program omits the closing fallback tags when saving and you get the error. It’s not your fault, but Microsoft has not been able to find and eliminate this bug since the 2007 version.
Are you managing styles in your Word documents? A hallmark of a professionally-created template is the appearance of the Quick Style Gallery. If I open a template and see this:
I realize the person who constructed the file doesn’t know better or doesn’t care. The clue are the 4 zombie styles on the right side. If you expand the gallery, you’ll see 8 more zombie styles. These 12 are automatically generated in every new installation of Word. Nobody uses them, they just clutter the interface. If you’re managing styles, you’ll make them disappear.
These 12 can’t be deleted, they are termed built-in styles and the Delete button is disabled in the style management dialog. But in Word for Windows, there is a Style Management panel called Recommended, where you can Hide them or optionally apply Hide Until Used. This last attribute keeps the style out of the Quick Style Gallery until the first time you apply it in a document, at which time it becomes visible.
But where is the Recommended panel in Word for Mac? Did someone Hide that too? No, it’s just not an option for Mac users. Microsoft left it out (speculate at will). But all is not lost: You can still manage style visibility on the Mac, you just have to do it with XML Hacking.
Begin by creating your template and creating the styles needed for that document. When you’re ready, we’re going to unzip the Word file, modify the XML, then re-zip the files. On a Mac, you have to take some extra steps to ensure that Mac attributes are not added to the files and folders by the Finder. Please take a moment to read my previous post about Editing XML in OS X
When you first open an Office XML field, the content is linearized and difficult to read. In BBEdit, apply Markup>Tidy>Reflow Document, leave the options at their defaults and click on the Reflow button. Voila! Readable XML!
Managing Styles with XML Editing
The style order in the XML file has nothing to do with the order of styles in the user interface, so it’s best to search for them. Start with the Title style. The default listing looks like this: (You may see a somewhat different collection of tags from different Word versions.)
<w:lsdException w:name="Title" w:semiHidden="0" w:uiPriority="10" w:unhideWhenUsed="0" w:qFormat="1"/>
The Styles list: a good place to display occasionally-required typestyles.
To make this style disappear from the Quick Style Gallery, but still appear on the Styles list, just delete the w:qFormat="1" tag. If you want to remove a style not only from the Quick Style Gallery, but also from the master list of recommended styles, then don’t bother with w:qFormat="1", just remove w:semiHidden="0". Finally, to give the style the ability to remain on the Styles list, then be added to the Quick Style Gallery when it is first used, leave the other tags as is and change w:unhideWhenUsed="0" to w:unhideWhenUsed="1".
Besides the Title style, the other zombie styles you’ll probably want to remove are:
Book Title and
Another useful edit you can make to styles is to change the number beside w:uiPriority. Decreasing this number moves a style up the list, while increasing it moves it down. For all styles that have the same level number, they are displayed in alphabetical order. I usually rank them in the order they are likely to be used, with the body text and headings at the top, followed by bulleted, numbered and lettered styles. Often you’ll have styles that serve a function in a Word file, like unique styles that are referenced by StyleRef fields. If the user doesn’t need to apply a style, hide it. The simpler you make their interface, the fewer mistakes they can make.
Save the XML file, then in the finder select [Content_Types].xml plus the folders. Right-click and choose Compress 4 Items. Change the ending of the resulting Zip file to .docx and click on the Use .docx button when OS X asks. Open the file and check out the beautifully clean Quick Style Gallery, thanks to you managing styles!
When you’re hand-editing Office files in Windows, it’s pretty straight-forward: unzip file > edit > rezip, you’re done. Editing in OS X requires a couple of extra precautions needed. This is because the graphical user interface adds Mac attributes to files and plants hidden files in folders. Office will not tolerate either of these:
XML error message in 2008
XML error message in 2011
XML error message in 2016
If you use OS X’s Archive Utility to unzip or zip the files, Word will refuse to open the resulting file. On top of that, if you look in any of the folders using the Finder, a hidden .DS_Store file will be created in the folder. When re-zipped, Word will not accept the extra file and again report an XML error. The solution to these issues is to use the command line, like the Unix warrior you want to be! Remember to run each Terminal command by pressing the Return key after typing the command.
A valuable utility for this is OpenTerminalHere. Open any Finder window, click on OpenTerminalHere and a terminal window opens pointed to the Finder window. So download and install it, then follow these steps to open, edit and re-zip Office files:
- Move a copy of the Office document (let’s call it TestDoc.docx) to a separate folder and open that folder in the Finder.
- Click on OpenTerminalHere to open a copy of Terminal aimed at the folder.
- In the Terminal, type
then press Return. The file is unzipped into several folders plus a file called [Content_Types].xml.
- Do not look in any of the folders using the Finder, or you’ll have to start over. To examine a folder’s contents, use the Terminal to change the folder, then list the contents:
- To go back up to the previous folder, type:
- To edit the files, open your text editor, then navigate using the File>Open dialog to find the file. Edit the file, then save and close.
- When you’re all done, double-check that terminal is pointing at the original folder holding the documents and the expanded folders. If you’re unsure, close terminal, then click on OpenTerminalHere to reopen in the right spot.
- In Terminal, re-zip the files with this style of command:
zip -r RevisedDoc.dotx [Content_Types].xml _rels docProps word
This example is for Word, but the correct syntax after zip -r is to type the name of the final document, followed by the file and folders, each separated by a space. The file is reassembled into an Office file.
- Test that you can open it. If you get an XML error notice, re-read the above steps and try again.
Please note: these editing techniques are required when editing in OS X with Word, PowerPoint and Excel documents and templates, plus Office Theme files (the kind exported from PowerPoint that combine all Theme elements.
If, on the other hand, you are editing a Font Theme or a Color Theme, those are simple XML files. They don’t need to be unzipped or re-zipped and Office doesn’t seem to care about OS X attributes attached to them. These plain XML files don’t need to be handled through the terminal, just use the Finder.
Next time, we’ll be looking at managing Word styles in OS X. Finally, a way to get rid of the zombie styles automatically created by Word! Happy hacking!
March 2016 Update
An (somewhat lame) alternative to working entirely in Terminal is to work on a network disk. Then you can open Terminal in your choice of folder and run the command:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
While this will prevent future generation of the .DS_Store files in that folder and any subfolders, it’s very likely you already have such files, since they’re created almost as soon as you view a folder’s contents in the Finder. So I recommend that while Terminal is open, you also run:
defaults write com.apple.finder AppleShowAllFiles YES
The second line restarts the finder to force a refresh of the view. Now you can see any .DS_Store files and delete them before re-zipping the files into an Office document. You’ll have still have to do the zipping in Terminal. Also, no .DS_Store files means OpenTerminalHere doesn’t work, so you’ll have to navigate manually via Terminal commands. Now you know why this is a lame alternative.
If you try this technique, you can always restore the clean file view by running:
defaults write com.apple.finder AppleShowAllFiles NO
May 2016 Update
BBEdit 11 now has the ability to open and edit Office files directly, avoiding all of the above hassle. However, you still have to be a little careful about your working procedure:
- Open your Office file in BBEdit 11. In the left-hand pane, you’ll see a folder tree of the files contained within, so no unzipping is required
- Select the file you want to edit. The file opens in the main BBEdit window, displaying two lines. The first is the XML header, the second is the actual content.
- Click at the left end of the second line.
- Choose Markup>Utilities>Format… (Format with three dots after it, the plain Format command will wreck your document!)
- Very Important: Uncheck the first Option Normalize tag case. Leaving this option checked will cause Office to see an XML error in the file!
- Change Mode to Strict Hierarchical and click on Format. The XML is formatted as indented multi-line text.
Make your edits and save. It’s not necessary to linearize the XML. The Office program will do that anyway the first time you save it. However, if you like to leave things exactly the way you found them, click in from of the first line of content (after the header line), choose Markup>Utilities>Format… again, change the Mode to Compact and click on the Format button. Save the file and test.