WordPress.org

Make WordPress Core

Changeset 40866


Ignore:
Timestamp:
06/01/17 09:48:41 (3 months ago)
Author:
ocean90
Message:

I18N: Improve translator comments for strings in the community events widget.

Props dimadin, iandunn.
Fixes #40865.

Location:
trunk/src
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-admin/includes/dashboard.php

    r40822 r40866  
    11701170                    <?php _e( 'City:' ); ?> 
    11711171                </label> 
    1172                 <?php /* translators: Replace with the name of a city in your locale that shows events. Use only the city name itself, without any region or country. Use the endonym instead of the English name. */ ?> 
     1172                <?php 
     1173                /* translators: Replace with a city related to your locale. 
     1174                 * Test that it matches the expected location and has upcoming 
     1175                 * events before including it. If no cities related to your 
     1176                 * locale have events, then use a city related to your locale 
     1177                 * that would be recognizable to most users. Use only the city 
     1178                 * name itself, without any region or country. Use the endonym 
     1179                 * (native locale name) instead of the English name if possible. 
     1180                 */ 
     1181                ?> 
    11731182                <input id="community-events-location" class="regular-text" type="text" name="community-events-location" placeholder="<?php esc_attr_e( 'Cincinnati' ); ?>" /> 
    11741183 
     
    12071216    <script id="tmpl-community-events-could-not-locate" type="text/template"> 
    12081217        <?php printf( 
    1209             /* translators: %s is the name of the city we couldn't locate. Replace the examples with cities in your locale, but test that they match the expected location before including them. Use endonyms (native locale names) whenever possible. */ 
     1218            /* translators: %s is the name of the city we couldn't locate. 
     1219             * Replace the examples with cities in your locale, but test 
     1220             * that they match the expected location before including them. 
     1221             * Use endonyms (native locale names) whenever possible. 
     1222             */ 
    12101223            __( 'We couldn&#8217;t locate %s. Please try another nearby city. For example: Kansas City; Springfield; Portland.' ), 
    12111224            '<em>{{data.unknownCity}}</em>' 
  • trunk/src/wp-includes/script-loader.php

    r40790 r40866  
    10471047             * to the user, so it's left as an implication. 
    10481048             */ 
    1049             /* translators: %s is the name of the city we couldn't locate. Replace the examples with cities in your locale, but test that they match the expected location before including them. Use endonyms (native locale names) whenever possible. */ 
     1049            /* translators: %s is the name of the city we couldn't locate. 
     1050             * Replace the examples with cities related to your locale. Test that 
     1051             * they match the expected location and have upcoming events before 
     1052             * including them. If no cities related to your locale have events, 
     1053             * then use cities related to your locale that would be recognizable 
     1054             * to most users. Use only the city name itself, without any region 
     1055             * or country. Use the endonym (native locale name) instead of the 
     1056             * English name if possible. 
     1057             */ 
    10501058            'could_not_locate_city' => __( 'We couldn&#8217;t locate %s. Please try another nearby city. For example: Kansas City; Springfield; Portland.' ), 
    10511059 
Note: See TracChangeset for help on using the changeset viewer.