[buddypress-trac] [BuddyPress Trac] #6149: i18n strings logical issues

[buddypress-trac]

#6149: i18n strings logical issues
--------------------------+------------------
 Reporter:  slaFFik       |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  2.3
Component:  i18n          |     Version:
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |
--------------------------+------------------
Changes (by boonebgorges):

 * milestone:  Future Release => 2.3


Comment:

 Thanks very much for the specific examples, @slaFFik.

 For the screen-reader-text, we can probably safely remove the translatable
 string altogether, and replace it with the component name. If someone
 thinks it's extremely important to have a verb in here, let's use the
 format 'Select component: %s', which is not terribly elegant, but should
 decline OK in most languages.

 The 'Edit Group' link should either be changed to a string literal 'Edit
 Group' (with no group name), or a colon should be added 'Edit Group: %s'.

 A general rule here is that we should never sprintf part of an English
 sentence. Nouns decline differently in different languages, verbs
 conjugate in ways we can't predict, etc. We should only sprintf stuff like
 URLs, CSS classes, etc. I'm guessing that most of the cases of `sprintf()`
 or `printf()` follow this rule, but there are probably many places where
 we can improve.

 I'm going to move this ticket to 2.3 so that we can handle the specific
 strings listed here. As you continue to find more, please post them on
 this ticket.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6149#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac