Page MenuHomePhabricator

Use 'email' instead of 'e-mail' for English messages
Closed, ResolvedPublic

Description

My observation is that 'email' is now a lot more common than 'e-mail' online, and Wikipedia corroborates this (https://en.wikipedia.org/wiki/Email#Spelling).

I think this will make people feel just a little more comfortable, so I propose changing our standard to be 'email'.

I don't think this is an American/British issue, since the Oxford dictionaries have 'email' canonical too according to http://oxforddictionaries.com/definition/english/email


Version: 1.21.x
Severity: enhancement

Details

Reference
bz45461

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 1:29 AM
bzimport added a project: MediaWiki-Interface.
bzimport set Reference to bz45461.

swalling wrote:

Very much needed. If even the staid OED and other sources (like the AP Stylebook) are switching to no hyphen, it's time we did too.

Will take care of this in the coming weeks. Means changes to dozens of extensions, so please allow me some time.

"E-mail" is surely easier to learn/understand/pronounce for non-native English speakers than "email".

MZMcBride, unfortunately, there are a lot of English words that are hard to pronounce. But pronunciation is not really that relevant when you're privately reading something anyway.

More importantly, our goal for the messages should be that they read as normal spelling and phrasing for the language in question. And 'email', without a dash, is now the norm for online English.

Besides using other language editions of the sites, people have the option to change their interface language in the preferences.

Patch sets done for core and 188 extensions that I have cloned. We may be getting some more fixes eventually.

http://hexm.de/45461 now has 29 patch sets that I'll start merging once I fix the issue that Raimond pointed out in core.

(In reply to comment #6)

http://hexm.de/45461 now has 29 patch sets that I'll start merging once I fix
the issue that Raimond pointed out in core.

28 patch sets were merged, the one for SemanticMediaWiki was not needed. This will be part of MediaWiki 1.21wmf11, and MediaWiki 1.21.0.

Iae47a24127b4bdd4ef308bdbd5be865217eb14f1, for reference.

Missed includes/installer/Installer.i18n.php.

(In reply to comment #9)

Missed includes/installer/Installer.i18n.php.

Gerrit change 51882

(In reply to comment #10)

(In reply to comment #9)

Missed includes/installer/Installer.i18n.php.

Gerrit change #51882

Merged by Siebrand.

Shouldn't all of the references to the word point to {{int:Email}} to allow quick and easy changing of it in the future as consensus declares?

(In reply to comment #12)

Shouldn't all of the references to the word point to {{int:Email}} to allow
quick and easy changing of it in the future as consensus declares?

I imagine many MediaWiki messages don't support {{int:Email}} expansion.

(In reply to comment #13)

(In reply to comment #12)

Shouldn't all of the references to the word point to {{int:Email}} to allow
quick and easy changing of it in the future as consensus declares?

I imagine many MediaWiki messages don't support {{int:Email}} expansion.

Then shouldn't they?

(In reply to comment #14)

(In reply to comment #13)

I imagine many MediaWiki messages don't support {{int:Email}} expansion.

Then shouldn't they?

Maybe, but I think it's irrelevant: the spelling shouldn't change often enough to warrant using a template.

(In reply to comment #15)

(In reply to comment #14)

(In reply to comment #13)

I imagine many MediaWiki messages don't support {{int:Email}} expansion.

Then shouldn't they?

Maybe, but I think it's irrelevant: the spelling shouldn't change often
enough
to warrant using a template.

Isn't that the reason that {{int:Email}} exists in the first place? Why would it be created and not used? Seems counter productive.

(In reply to comment #16)

Isn't that the reason that {{int:Email}} exists in the first place? Why
would
it be created and not used? Seems counter productive.

No, that is not why the message key "email" exists. It exists because it is used in a certain context. Templates should not be used in localization, because it inhibits translation. It is not counter productive, even though it may seem to be to you.