Skip to content
This repository was archived by the owner on Oct 9, 2018. It is now read-only.

Style guide should define whether or not to use abbreviations in error messages (e.g."can't" vs "can not") #38

Open
kud1ing opened this issue Dec 30, 2014 · 2 comments

Comments

@kud1ing
Copy link

kud1ing commented Dec 30, 2014

We're using "can't" and "can not" in error messages. I think for consistency we should settle on one.

@pyfisch
Copy link

pyfisch commented Jan 7, 2015

I think, that we should use always "can not" since documentation is usually written in formal language.
This also applies for all other short forms like for example "isn't".

@chris-morgan
Copy link
Member

Bear in mind that “can not” is ambiguous in some locales; in consequence, it should never be; the unambiguous “cannot” should instead be used.

I contest that documentation is usually or should be written in rigidly formal language; I believe “can’t” to be entirely acceptable. (This simply leaves me ambivalent about which direction it goes.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants