Changeset 40866

Timestamp:

06/01/2017 09:48:41 AM (8 years ago)

Author:

ocean90

Message:

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

Props dimadin, iandunn.
Fixes #40865.

Location:

trunk/src

Files:

• wp-admin/includes/dashboard.php (modified) (2 diffs)
• wp-includes/script-loader.php (modified) (1 diff)

trunk/src/wp-admin/includes/dashboard.php

@@ -1170 +1170 @@
                     <?php _e( 'City:' ); ?>
                 </label>
-                <?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. */ ?>
+                <?php
+                /* translators: Replace with a city related to your locale.
+                 * Test that it matches the expected location and has upcoming
+                 * events before including it. If no cities related to your
+                 * locale have events, then use a city related to your locale
+                 * that would be recognizable to most users. Use only the city
+                 * name itself, without any region or country. Use the endonym
+                 * (native locale name) instead of the English name if possible.
+                 */
+                ?>
                 <input id="community-events-location" class="regular-text" type="text" name="community-events-location" placeholder="<?php esc_attr_e( 'Cincinnati' ); ?>" />
 
@@ -1207 +1216 @@
     <script id="tmpl-community-events-could-not-locate" type="text/template">
         <?php printf(
-            /* 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. */
+            /* 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.
+             */
             __( 'We couldn&#8217;t locate %s. Please try another nearby city. For example: Kansas City; Springfield; Portland.' ),
             '<em>{{data.unknownCity}}</em>'

trunk/src/wp-includes/script-loader.php

@@ -1047 +1047 @@
              * to the user, so it's left as an implication.
              */
-            /* 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. */
+            /* translators: %s is the name of the city we couldn't locate.
+             * Replace the examples with cities related to your locale. Test that
+             * they match the expected location and have upcoming events before
+             * including them. If no cities related to your locale have events,
+             * then use cities related to your locale that would be recognizable
+             * to most users. Use only the city name itself, without any region
+             * or country. Use the endonym (native locale name) instead of the
+             * English name if possible.
+             */
             'could_not_locate_city' => __( 'We couldn’t locate %s. Please try another nearby city. For example: Kansas City; Springfield; Portland.' ),