Spotted in a Facebook editors’ group, with no attribution, unfortunately. Thanks to the person who put this together. My daily work life is definitely the bottom right image!
My husband has an 80-page table in Word (don’t ask! yes, one table, about 7 columns, lots of tabular data, and in 7-point font size zoomed in to 150%) that he needs to sort in all sorts of different ways at various times. He was complaining that it wouldn’t sort properly and that when he selected the whole table to sort or do a find/replace, the table would move to another location in the document as evidenced by the first Undo command being the option choice to undo the move.
I watched exactly what he did—he selected the table using the mouse by clicking on the little grid selection icon at the top left of it, clicked the Sort icon on the Home tab, specified the sort order, then clicked OK. He rarely uses any keyboard commands, so only the mouse was used for all this.
First, the sort order that results didn’t match up with what he wanted. He wanted to sort by column 1, which had 4-digit years. The first date listed in the sorted table was 1984, yet he had dates from 1959 through to 2020 in that column. We tried redoing the sort using a text sort, a number sort, and a date sort, and ascending and descending order, getting different results each time, but nothing that reflected the dates he has in that column.
Then I watched as he did a search for a word, then selected the table again by clicking on the little grid icon at the top left of the table. This time there was a strange movement/cut off the page thing that happened (he wasn’t touching any keys), and the table looked a bit odd. It had moved to another location in the document! He hovered over the Undo command and sure enough, there was the option to undo the move. There is NOTHING that he did that would have caused that table to move!
I watched him do variations on this several times, each time not getting a correct sort and/or moving the table without his intervention.
I thought I’d get him to try something else—select the table from the Table Tools > Layout tab, under Select > Select Table. This time the table sorted correctly AND it didn’t move.
I have no idea what happened but selecting by another means seems to have solved the problem—I hope!
Update: In her comment below, Lene Fredborg suggested that clicking that table selection control might cause the table wrapping to go from ‘none’ to ‘around’ (right-click, Table Properties, Text wrapping), and that’s exactly what happened when I tested it myself. I wonder if this is a bug?
In the main, British English and American English treat punctuation at the end of speech quotation marks differently—US English has the punctuation inside the final quotation mark, whereas British English has it outside (there may be some exceptions to this general rule, but let’s just go with what usually happens).
If you need to style speech from British English to US English, you need to find all the various punctuation marks that come after a quotation mark and transpose them so they come before the quotation mark. You can do with with a find and replace using wildcards.
These instructions are for Word for Windows, but you should be able to do something similar in Word for Mac.
How this works:
An aptronym is where a name matches some characteristic of a person, typically their occupation. The first I ever experienced was when I was a kid—the town’s only butcher was… Mr Butcher!
More recently, I’ve come across other names that match their occupations or areas of expertise. For example, authors Whiting and Salmon have both written on fish, Swann has written on birds, and today I came across Fangue, who has co-authored an article on a species of sea krait!
See also: https://cybertext.wordpress.com/2013/10/23/names-suiting-occupation/
I was working on a big Word document (570 A4 pages, 220,000 words, oil and gas report) and needed to spellcheck it. But straight away, spellcheck started doing weird things, like only ‘seeing’ part of a word. For example, for a word like ‘process’, it wouldn’t recognise the ‘p’ and so reported ‘rocess’ as incorrect. This wasn’t a one-off either—I was seeing this behaviour in almost every word that spellcheck caught.
I thought it might be to do with track changes, so I showed all markup. But no. These words hadn’t been changed at all, and were several lines or paras removed from anything that had been changed.
Next, I wondered if it was to do with the file size and the fact that I had various large Word docs open at the same time. It was the end of the day so I shut down my computer, and decided to try again in the morning. First thing next day, I started the spellcheck, but with no change—it was still reporting parts of words as incorrectly spelled. I checked the language setting on the status bar, but it was correct (sometimes Word will report a partial word as incorrect because a different language is applied to it).
Then I decided to try something I do on most of the docs I work on, but hadn’t done on this one as yet—run the two macros I have for setting the language for most elements (https://cybertext.wordpress.com/2011/10/14/word-macro-to-set-the-language-for-most-eleme/) and for all styles (https://cybertext.wordpress.com/2018/09/21/word-macro-to-set-the-language-for-all-styles/). Even on a big document like this, these macros took only a minute to run.
I tried spellcheck again, and it worked as it should!
So I can only assume that a language setting was applied to something in the document (possibly a style?) that spellcheck didn’t recognise as Australian English, my version of English.
Jeremy wanted to change how his page numbers were punctuated. He needed to change instances such as ‘p152’, ‘p24’ etc. to ‘-p. 152.’, ‘-p. 24.’—that is, he wanted to add a dash in front of the ‘p’, a period and a space after the ‘p’, and a period at the end of the number. I didn’t know what his number range extended to, so I created the Find string to include any of one to four numbers.
This is an easy thing to do using Word’s wildcard find and replace, but there are some warnings: