-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replaced 'telephone' with 'phone' where I could. It needs further review #1793
base: main
Are you sure you want to change the base?
Replaced 'telephone' with 'phone' where I could. It needs further review #1793
Conversation
✅ You can preview this change here:Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @terrysimpson99, thanks for flagging this up, I'm asking around and having a think about this. GOV.UK style guide suggests that both are fine — from a quick chat with some content folks, 'phone' is probably simpler, however 'telephone' might be clearer for people who do not speak English as a first language, as the word is similar in many other languages. For the Design System guidance, my thinking right now is to look at it in terms of formalness and perhaps use both where appropriate — for example use 'telephone' in high-level headings or names of services and use 'phone' in more casual mentions. |
I'm happy people are thinking about the issue. I thought about it quite a bit. The current situation is that both are used but that's an accident. I think it would be quite difficult to create, describe, or audit a rule where 'telephone' is deliberately used in some places and 'phone' is deliberately used in others. My suggestion would be to make a decision to use a single term throughout. That's an easy rule to create, describe and audit. Exceptions are always possible. I don't know if 'phone' is more difficult than 'telephone' for people who do not speak English as a first language. I note the point about 'telephone' being similar to non-english words. If this is true, it will influence my thinking. I'll ask around on slack. |
On previous occasions, the Slack consensus has been in favour of using 'phone'. Your (Calvin) comment relates to a small but important group of people that may be helped by going in the other direction. I've thought about it more and discussed that specific point with others on Slack. I think the balance of risk and consequence remains in favour of eliminating inconsistency and using 'phone' throughout. I'll leave it up to GDS content designers to decide. Thanks. |
…iew. The Design System and content guidance use both 'telephone' and 'phone' as synonyms. Guidance can be made consistent by using one term throughout. Google ngram viewer indicates 'phone' is dominant (https://books.google.com/ngrams/graph?content=phone%2Ctelephone&year_start=1800&year_end=2019&corpus=29&smoothing=3). Discussions on Slack and on github (alphagov/govuk-design-system-backlog#101 (comment)) indicate the single term 'phone' can be used throughout.
df93cdf
to
5b6b9ce
Compare
Just given this PR branch a rebase to avoid conflicts |
The Design System and content guidance use both 'telephone' and 'phone' as synonyms. Guidance can be made consistent by using one term throughout. Google ngram viewer indicates 'phone' is dominant (https://books.google.com/ngrams/graph?content=phone%2Ctelephone&year_start=1800&year_end=2019&corpus=29&smoothing=3). Discussions on Slack and on github (alphagov/govuk-design-system-backlog#101 (comment)) indicate the single term 'phone' can be used throughout.