A family of Microsoft word processing software products for creating web, email, and print documents.
To add to what Charles suggested, some people like to display crop marks as well (File | Options | Advanced: "Show crop marks").
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just upgraded from Word 2007 to Word 2013. In the 2007 version, I could display the margins but I haven't been able to find how to do that in Word 2013. Does anyone know? Clicking on "show text boundaries" seems to put a lot of lines in the document only.
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
To add to what Charles suggested, some people like to display crop marks as well (File | Options | Advanced: "Show crop marks").
***
Now if someone could tell me the "work around" for newspaper colunns, that would help.
***
View rulers helps, as does viewing non-printing formatting marks.
There are items that are hard to believe! Never was intended? Then why was Text Boundaries in so many versions before it was "caught"?
I think "text boundareis" were intended, but someone "goofed" on this version, must have been pretty high up, and will not take the credit or blame for changing "text boundareis"!
For the records, I just did newspaper columns the other day, three columns, and could not figure out a way to know where the "text boundaries" happened to be.
I did run a line between the columns, but that did not tell where the text would stop and start. If one wants to place a text box or a picture on either margin, it sure would be nice to have the line for the margin!!!!
The "work around" for mailing labels - "veiw gridlines" in tables works.
Now if someone could tell me the "work around" for newspaper colunns, that would help.
Bug or not, intended or not, just bring "text boundaries" back!
And thanks for all the support of those making a contribution to this item.
As a computer programmer, I was taught to categorize a part of a program that did something inadvertent or unintentional as a "bug". And calling something a bug (in my book) is synonymous with saying that the program is broken. Broken does not mean that the program has to crash/abend, just that it simply is not giving the desired result.
I think we are generally in the same ball park.
There's a difference between something that was inadvertent or unintentional to begin with or "a mistake" and something that was "broken."