[wp-meta] [Making WordPress.org] #6922: Translate: missing translators comments from Gutenberg

Making WordPress.org noreply at wordpress.org
Tue Apr 11 11:32:19 UTC 2023


#6922: Translate: missing translators comments from Gutenberg
--------------------------------------+---------------------
 Reporter:  afercia                   |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by aristath):

 Did some quick investigation, looking at the way these files get compiled.

 The code in `gutenberg/packages/editor/src/components/table-of-
 contents/index.js` contains the `Details` string like this:
 {{{
         aria-haspopup="true"
         /* translators: button label text should, if possible, be under 16
 characters. */
         label={ __( 'Details' ) }
 }}}
 However, when the files get compiled, the result looks like this:
 {{{
         "aria-haspopup": "true"
         /* translators: button label text should, if possible, be under 16
 characters. */
         ,
         label: (0,external_wp_i18n_namespaceObject.__)('Details'),
 }}}
 There's an extra line between the comment and the actual string. In this
 case that line contains a comma, but in other cases I looked at it was a
 plain blank line. Strings that don't have any additional lines between the
 comment and the string seem to have the translators comment properly used,
 while strings that have additional lines between the comment and the
 string don't - regardless of whether that line is a plain blank line or a
 comma etc.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6922#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list