One thing that's nice about being a programmer is that I haven't thought about any mechanics of text formatting for many years. When I save a file, it just gets reformatted according to rules that were set up exactly once. I have no idea whether or not I use spaces or tabs, or whether there are semicolons at the end of lines, or whether it's "} else {" or "}\nelse {". It makes me sad that the least technical users ha…
Being a programmer won't save you from this particular style war. If there's a comment in your code with a sentence that begins with a double space, your code formatter probably won't flag or remove it in the same way that MS Word will. And it's likely shown in a monospace font, which makes it more noticeable. How many spaces do people put after a full stop in comments in their code? I go with one, but Vim's J and gq…
Microsoft Word now flags double spaces after a period as errors
261–270 of 270 posts
Re: Microsoft Word now flags double spaces after a period as errors
#262Earlier quoted context omitted.
They are using markup where they shouldn't be. If, in word, I type italic text using stars, that just means I'm wrong in that context. Similarly, if I use escapes, such that I expect \n to add a new line, I'm just wrong. That doesn't make it less useful where it originated. Edit: I amusingly had to try twice to get the italic text there. Double stars did not bold. I don't know how to escape the stars.
Word has never had markup though. Nor have most people ever written markup. Why would they be trying to write markup?
Just like most people that write on paper don't leave extra space after a sentence. We do indent paragraphs commonly. At least, if you are writing somewhere you want it indented, it is incumbent on you to do so. :)
Re: Microsoft Word now flags double spaces after a period as errors
#263Earlier quoted context omitted.
Excellent suggestion. How could I have forgotten about half-width spaces?
This would only work when editing, not when typing it out the first time.
Re: Microsoft Word now flags double spaces after a period as errors
#264Earlier quoted context omitted.
Do any code editors also treat a delete of one of these spaces as removing the tab width size? (I've never seen it, but maybe there are ones that do that.) What tends to happen is that yes, the tab enters the N spaces, but if you have to move code around, you can find yourself deleting a lot of spaces.
I'm using VS Code and it does do that. It deletes back to the previous indentation level. In the case when you move code around you will anyway go for Tab/Shift+Tab in any editor.
Re: Microsoft Word now flags double spaces after a period as errors
#265Earlier quoted context omitted.
A friend of mine is a physics PhD. Most journals require to use their exact LaTeX settings for every little detail in order to have an article published. Which means quite a lot of menial work to redo the article each time you apply, get refused, and want to send to another journal.
> Which means quite a lot of menial work to redo the article each time you apply, get refused, and want to send to another journal. What kind of menial work do you mean? Isn't that just a matter of changing the class of your document? Why would you need to change the text of the article itself?
Not to mention often the latex style (or word template) given often directly contradicts the author instructions page on the website.
Re: Microsoft Word now flags double spaces after a period as errors
#266Earlier quoted context omitted.
One of the comments there concisely summarizes history better than modern typographers do: > I think most books don't do this any more [have wider spaces between sentences]. Newspapers certainly don't. It's way too much trouble escaping out all the abbreviations. If you need wider spaces between sentences you also don't want them indiscriminately after every period, so you need to exercise more care and indicate them…
Note: You should use nonbreaking spaces (the ~) in many places where they are often not used.
Re: Microsoft Word now flags double spaces after a period as errors
#267Earlier quoted context omitted.
Wait, what's the \null for and shouldn't there be a \ after Soc.?
Yes there should be a \ after “Soc.” Proofreading the typeset output might have caught this error. :-) The “\null” after “NASA” is to show an example where the heuristic fails in the other direction: the “.” after the uppercase letter won't be considered to end the sentence, so you need to either type `\hbox{NASA}.` or `NASA\null.` (where `\null` is an abbreviation for `\hbox{}` i.e. an empty box) or something like t…
Re: Microsoft Word now flags double spaces after a period as errors
#268Earlier quoted context omitted.
I don’t know. It sounds like you’re older and smarter than I, but whenever I see two spaces at the end of a sentence, I fix it to make it one space. It looks plain wrong to my brain
Double spacing between paragraphs is surprisingly helpful with smudged text on physical paper. Many linguistic conventions seem arbitrary, but are really about redundancy. Punctuation could have replaced spaces.just like capitalization of the first letter in a new sentence,it’s helpful to make things as obvious as possible. Is that period a typo or are those supposed to be different sentences?
Re: Microsoft Word now flags double spaces after a period as errors
#269Earlier quoted context omitted.
Please can you give an example? That would make your point easier to understand
Especially the overloaded ".". Apart from usage as a decimal point and elipsis, where it's obvious, what are the overloaded cases?
Re: Microsoft Word now flags double spaces after a period as errors
#270Earlier quoted context omitted.
Yes there should be a \ after “Soc.” Proofreading the typeset output might have caught this error. :-) The “\null” after “NASA” is to show an example where the heuristic fails in the other direction: the “.” after the uppercase letter won't be considered to end the sentence, so you need to either type `\hbox{NASA}.` or `NASA\null.` (where `\null` is an abbreviation for `\hbox{}` i.e. an empty box) or something like t…
I think `\relax` is a better no-op than `\null`, right?