Header error on .docx compile (box around header)

This is relatively low importance since it’s easy enough to compile into .rtf and change the format in Word. Perhaps even preferable, I don’t know. Just reporting that when I compile a document to .docx, I get a box around the header info. Unless this is intentional, although I’ve never seen this as any kind of standard.


Running Version: - 11 Mar 2015, Windows 7.

Have you checked to make sure Word itself isn’t drawing the box (printing preview from Word is the best way to check)?

Just now coming back to this after noticing the latest update to the s/w. I’m not sure how I would determine that. The box is there on the screen when I open the .docx file immediately after compiling. I don’t need to look at print preview to see it. It isn’t there in an .rtf file after compiling so I have a tendency to assume it is something in the .docx compile process, vs. something Word is doing. It would seem, to me, that if Word is going to, by default, draw boxes around my headers, it would do it every time I open a .docx file and not just a .docx file created by Scrivener. That is not the case. Now that doesn’t mean it isn’t Word working in concert with/against Scrivener’s instructions. Only that the two are not necessarily playing nicely in this instance.

As I said, it’s not a big deal. Clearly I’ve forgotten all about it. :wink: Just a weird little thing that appeared as I was working.

I’m in Windows 7 still. Office 2007. Behind the times. Perhaps this would not be happening if I upgraded, but that’s not going to happen anytime soon. Good Lord! I just realized my software is eight years old. That’s a software sin, is it not? (hangs head in shame) :blush: Now I’m embarrassed I even brought it up.

Actually I’d say stick with 2007 or 2010 anyway, as the newer stuff doesn’t install libraries that we can use to create higher quality output. Besides, they are not based upon some “cloud” that you have to subscribe to every year. I don’t support that kind of stuff on general principle, but that’s just me.

At any rate, the reason for asking whether it shows up in print preview was not to merely see it again, but to see if it doesn’t show up on paper. My speculation is that you’re looking at some kind of Word markup, equivalent to showing invisible characters in the editor. Nearly if not all of the questions we get about MS Word drawing brackets, boxes, lines, squiggles, dots and other paraphernalia come down to some display setting in Word indicating rich content that Scrivener produced, not actual squiggles and boxes (which Scrivener has zero code to generate in the first place).

While the Office 365 for Home product is indeed a subscription-based version of the Office suite, you can still buy a regular Office SKU that installs one-time and works until you change the computer or get rid of it.

The compile converter works with MS Office 2007, 2010, and 2013. Office 365, because it has completely different APIs, does not work, no matter which flavour you’re using.

I’m sorry, but that’s incorrect. The version of Office that you download from Office 365 (whether Office 365 ProPlus as part of a business Office 365 services tenant, or via Office 365 for Home which is confusingly named but is essentially a downloaded, auto-updated version of the Office suite) is still Office and it still includes basically the same binaries and APIs. All of my Office add-ons that worked on Office 2010 continue to work on my Office 2013/2016 Office 365 for Home install. Scrivener still uses my Office 2013/2016 Office 365 for Home install, just like it used my Office 2010 install.

I make my living working with Office 365 in all its forms. I’m not trying to push it on anyone, but people do need to see correct information so they can accurately choose the right software for their needs.