[wp-trac] [WordPress Trac] #41438: Add context to tab labels of Content and Text widget editors

[WordPress Trac]

#41438: Add context to tab labels of Content and Text widget editors
---------------------------+------------------------------
 Reporter:  pedromendonca  |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  I18N           |     Version:  4.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Description changed by SergeyBiryukov:

Old description:

> Add context to improve consistency of the strings of '''Visual''' and
> '''Text''' (formerly HTML) tab names of the content editor and the text
> widget editor, keeping it separate from generic strings.
>
> Because of its shorten names, for some languages these tab names
> translations might not be as simple and direct as it seems.
>
> The tab name '''Text''' means ''Text mode'', but it's not as clear as the
> old '''HTML''', and just '''Text''' oposing '''Visual''' might lead to
> some confusion, as both can be about ''text''.
>
> But this ticket isn't about opening this discussion, and that was already
> decided previously in this ticket:
> [https://core.trac.wordpress.org/ticket/20993].
>
> This ticket adds a context to these strings to allow the Translation
> Teams to choose the better translation for each, keeping the consistency
> between the tabs of the Text Widget editor and the Content Editor,
> without compromise the current translation of a generic string "Text" (or
> "Visual") that have the potencial to be used a lot within core and meta.
> Eg. '''Text''' Widget title
>
> '''Current Content editor tabs:'''
>
> {{{
> __( 'Visual' ), // Editor switch tab label
> __( 'Text' ), // Editor switch tab label
> }}}
>

> '''Current Text Widget editor tabs:'''
>
> {{{
> __('Visual')
> _x( 'Text', 'Name for the Text editor tab (formerly HTML)' )
> }}}
>

>
> '''Proposed Content/Text Widget editor tabs:'''
>
> {{{
> _x( 'Visual', 'Name for the Visual editor tab' )
> _x( 'Text', 'Name for the Text editor tab (formerly HTML)' )
> }}}

New description:

 Add context to improve consistency of the strings of '''Visual''' and
 '''Text''' (formerly HTML) tab names of the content editor and the text
 widget editor, keeping it separate from generic strings.

 Because of its shorten names, for some languages these tab names
 translations might not be as simple and direct as it seems.

 The tab name '''Text''' means ''Text mode'', but it's not as clear as the
 old '''HTML''', and just '''Text''' oposing '''Visual''' might lead to
 some confusion, as both can be about ''text''.

 But this ticket isn't about opening this discussion, and that was already
 decided previously in this ticket: #20993.

 This ticket adds a context to these strings to allow the Translation Teams
 to choose the better translation for each, keeping the consistency between
 the tabs of the Text Widget editor and the Content Editor, without
 compromise the current translation of a generic string "Text" (or
 "Visual") that have the potencial to be used a lot within core and meta.
 Eg. '''Text''' Widget title

 '''Current Content editor tabs:'''

 {{{
 __( 'Visual' ), // Editor switch tab label
 __( 'Text' ), // Editor switch tab label
 }}}


 '''Current Text Widget editor tabs:'''

 {{{
 __('Visual')
 _x( 'Text', 'Name for the Text editor tab (formerly HTML)' )
 }}}



 '''Proposed Content/Text Widget editor tabs:'''

 {{{
 _x( 'Visual', 'Name for the Visual editor tab' )
 _x( 'Text', 'Name for the Text editor tab (formerly HTML)' )
 }}}

--

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