Draft Font Issue

[Ross from Orlando]

I've been using Word 2013 for about a week. In Options, Advanced under "show document content" the box is unchecked next to "use draft font in draft and outline views." Somehow, inexplicably, the box now and then checks itself. I realize this whenever a document opens in draft view and the font is courier new.

I normally work in draft view. In fact, I have the macros in Jay Freedman'sanswer here: http://answers.microsoft.com/en-us/...-view-by/9290cb31-d8c4-4c9b-b711-0e520f28538b. They make all documents open in draft view. But I want them in the correct font, not the draft font.

Anyone else had this issue? Is it a known problem in Word 2013? Thanks,


Ross

 

[Stefan Blom]

Use the following two auto macros to force Draft view but suppress the draft
font:

Sub AutoOpen()
ActiveWindow.View.Draft = False
ActiveWindow.View.Type = wdNormalView
End Sub

Sub AutoNew()
ActiveWindow.View.Draft = False
ActiveWindow.View.Type = wdNormalView
End Sub

Store the macros in the Normal template.

 

[Ross from Orlando]

Use the following two auto macros to force Draft view but suppress the draft

font:



Sub AutoOpen()

ActiveWindow.View.Draft = False

ActiveWindow.View.Type = wdNormalView

End Sub



Sub AutoNew()

ActiveWindow.View.Draft = False

ActiveWindow.View.Type = wdNormalView

End Sub



Store the macros in the Normal template.



--

Stefan Blom

Microsoft Word MVP









in message

Thanks, Stefan, I have done this. One thing I notice is that when I start Word and the New Blank Document shows up it appears in Print View. When I open I new file, the macro makes it show up in Draft View (which is what I want). Is there a way to make the New Blank Document that shows up on starting Word appear in Draft View?

 

[Stefan Blom]

Unfortunately, it happens quite a lot that the auto macros fail when you
first start Word. Setting a "delay," so that Word gets loaded into memory
completely before the macro runs, should help in these situations. I have
experimented with this previously, but I'm afraid I don't have a working
example right now.