[wp-trac] [WordPress Trac] #34887: Standardize on front end (n.) and front-end (adj.)

[WordPress Trac]

#34887: Standardize on front end (n.) and front-end (adj.)
----------------------------------------+------------------------------
 Reporter:  ocean90                     |       Owner:
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Text Changes                |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  good-first-bug needs-patch  |     Focuses:
----------------------------------------+------------------------------

Comment (by obrienlabs):

 @ocean90 I'm doing some research on this, and it looks like (according to
 [http://english.stackexchange.com/a/34953 this post] from the English
 group at Stack Exchange) that `front end` is the right way to say it. The
 reasoning is front end refers to `that part of a hardware or software
 system that is closest to the user.`.

 [http://www.merriam-webster.com/dictionary/front%20end According to
 Merriam-Webster], and example of `front-end` is: `There is no front–end
 charge at the time of investment.`

 Best I can tell, `frontend, front-end and front end` within the WordPress
 files are referring to the part of the software system closest to the user
 - so it seems that it should be `front end`.

 I'm working on submitting a patch to reflect `front end`, but I have 2
 questions:

 1. Should I include themes? (e.g. front-end is found in twentytwelve,
 twentythirteen, twentyfourteen and twentyfifteen)
 2. By this same principle, should `back-end and backend` be standardized
 to `back end`? I'm finding inconsistencies there, too.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34887#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform