[wp-trac] [WordPress Trac] #47003: i18n: Merge similar translation strings in new user registration screen

[WordPress Trac]

#47003: i18n: Merge similar translation strings in new user registration screen
-------------------------------------------------+-------------------------
 Reporter:  ramiy                                |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  5.4
Component:  Users                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:
  refresh                                        |  administration
-------------------------------------------------+-------------------------
Changes (by garrett-eclipse):

 * keywords:  has-screenshots has-patch => has-screenshots has-patch needs-
     refresh
 * milestone:  5.3 => 5.4


Comment:

 @SergeyBiryukov made some good points and a proposal in #47656;
 > Previous discussion: #15887
 >
 > Specifically, I think comment:5:ticket:15887 sums up the purpose of the
 `ERROR:` prefix nicely:
 > > All CAPITAL letters in a word
 [http://english.stackexchange.com/q/8672/3574 typically denotes Emphasis].
 It's not meant to be
 > >
 > > "Good day gentle, but incorrect, user - there seems to be an error. Be
 a sport and type in your e-mail address"
 > >
 > > But rather
 > >
 > > "HEY, USER! (yelling) THERE'S A PROBLEM! ATTENTION! ERROR. Type in
 your email address please"

 > We could, however, move the `ERROR:` prefix out of the strings and add
 it separately, see the error message in [source:tags/5.2.2/src/wp-
 admin/themes.php?marks=231#L229 wp-admin/themes.php] for example. Related:
 #38860

 I concur and believe isolating the prefix is our patch forward here.
 @ramiy would you like to handle the refresh?

 As it will need a refresh and would be a string change I would feel more
 comfortable tackling this in 5.4 as we're already in beta2 for 5.3, as
 well that allows us to coincide #47656 as I'm marking it for 5.4 as well.

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