[buddypress-trac] [BuddyPress Trac] #6951: Add comments for translators in accessibility strings

[buddypress-trac]

#6951: Add comments for translators in accessibility strings
--------------------------------------+-----------------------------
 Reporter:  slaFFik                   |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Locale                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |
--------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:5 mercime]:
 > I'm curious though why there's a need to add translator comments for
 simple two/three word accessibility strings in BuddyPress when the same is
 not needed in WordPress as seen throughout core source code for similar
 simple strings?

 Right, I don't think there's a precedent for similar comments in WordPress
 core. Generally we add comments for strings with placeholders:
 {{{
 /* translators: %s: Name of current post */
 sprintf( __( 'Continue reading %s' ), '<span class="screen-reader-text">'
 . get_the_title() . '</span>' )
 }}}
 or strings that have a special meaning:
 {{{
 /* translators: If there are characters in your language that are not
 supported
  * by Open Sans, translate this to 'off'. Do not translate into your own
 language.
  */
 if ( 'off' !== _x( 'on', 'Open Sans font: on or off' ) ) {
         ...
 }
 }}}

 For accessibility strings, the context usually seems obvious, and there's
 a source code reference for more details.

 So I'd like to know @slaFFik's reasoning as well :) Would you translate it
 differently with such a comment?

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