Have to vs must
-
That's what I thought, but when I checked the list of languages, there was only one selection for English - no English(UK) or similar. MSDN didn't indicate it exists either.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
Great example. But you shouldn't forget: You can not climb that wall (maybe another one?) :-D At least, sometimes interpunctuation comes to the rescue when you need to resolve an ambiguity: "Let's eat, grandpa" is fine, but "Let's eat grandpa" is cannibalistic :omg:
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
I admit that I haven't read through all of the replies so if someone else has made the same comment as I am about to make, then I apologise. Look at almost any of the RFC for the Internet standards (sorry, memory has gone it's something like IETF). They start with a section about the use of words like SHOULD, CAN and MUST. It is a good staring point. Re your samples
"I have to use the Azure cloud at work"
, I agree; but for
"I must work out more often"
I'd have suggested
"I ought to work out more often"
or
"I should work out more often"
to indicate that it is something that the general consensus is that there is pressure on you to do it but you can refuse.
-
Ah, found 'em! I must have looked in the wrong place. Only 16 kinds here, but it's Office 2013. :doh: I've also found Swiss German, and that appears to be solving my problem with that unwanted autocorrection using ß. :thumbsup:
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
Ah, found 'em! I must have looked in the wrong place. Only 16 kinds here, but it's Office 2013. :doh: I've also found Swiss German, and that appears to be solving my problem with that unwanted autocorrection using ß. :thumbsup:
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
Stefan_Lang wrote:
Only 16 kinds here, but it's Office 2013.
Stefan_Lang wrote:
I've also found Swiss German, and that appears to be solving my problem with that unwanted autocorrection using ß.
Well... it took only 7 years (at least) to find out and solve your problem :-D I really whish you don't have to look for "grammar" options in Intellisense :laugh: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Well, tell your cow-orkers that an expert has said that they have to say it your way. I'd be horrified to see support messages insultingly talking of "your problem" to customers, as if it were their fault.
I wanna be a eunuchs developer! Pass me a bread knife!
"The problem", "the issue", "what you're seeing"...I'm always willing, in my correspondence with customers, to shift the problem on us rather than something they're doing, even if nobody else has reported anything wrong. "Your problem" just *so* obviously sounds condescending to me.
-
"The problem", "the issue", "what you're seeing"...I'm always willing, in my correspondence with customers, to shift the problem on us rather than something they're doing, even if nobody else has reported anything wrong. "Your problem" just *so* obviously sounds condescending to me.
Exactly. Never forget that they're paying good money for service, so they should get good -- and, at very least, polite -- service.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I'm writing some stuff in Word and Word thinks it's necessary to improve my writing. Mostly, that's true, but it has one suggestion that I followed until I found out it's not right. Every time I write "have to" or some form of it, Word says "use 'must' for concise language." Now, as I understand it, that's perfectly fine in American English, but not so much in British English where "have to" indicates an external incentive while "must" comes from an internal incentive. For example, "I have to use the Azure cloud at work" (dictated by your boss) and "I must work out more often" (something you wish to do because it's healthy). Of course, if your doctor or wife tells you to work out more often "or else" it becomes "I have to work out more often." Anyway, I must now change "must" to "have to" or my readers will make fun of me for not understanding the English language :sigh: The issue is pretty much un-Googleable, but does anyone know how I can turn off this very specific "have to" to "must" rule?
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
I have Word Professional Plus 2016. I don't know if these instructions will be similar or not for your version. To use English (United Kingdom) instead of English (United States) 1) Open Word. 2) Click on File tab. 3) Select Options (bottom option on left menu bar). 4) Select Language (left menu bar). 5) Use drop-down list to "add additional editing language" and select "English (United Kingdom)". 6) Click Add. 7) In the Choose Editing Languages group, select English (United States). 8) Click Remove. 9) Click OK to exit. To stop having only this particular rule checked: 1) I can't find it. 2) Just turn off grammar checking instead :) Bond Keep all things a simple as possible, but no simpler. -said someone, somewhere
-
There is a reason why these terms are explicitly defined (in its own RFC, if my memory is right): The terms can be understood in different ways, but in this context, this RFC, they have this meaning: ... Sort of a "YMMV" declaration.
-
whilst I agree with your sentiment...
I don't need some American software who thinks it knows better
is grammatically incorrect. The American software is inanimate. 'who' should be 'that'
Live long and prosper
