Make WordPress Core


Ignore:
Timestamp:
09/01/2019 05:12:43 PM (7 years ago)
Author:
SergeyBiryukov
Message:

I18N: Improve translator comments.

  • Add missing translator comments.
  • Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various .pot file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.

Includes minor code layout fixes.

Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!

Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-admin/setup-config.php

    r45737 r45926  
    170170<p>
    171171                <?php
    172                 /* translators: %s: wp-config.php */
    173172                printf(
     173                        /* translators: %s: wp-config.php */
    174174                        __( 'We&#8217;re going to use this information to create a %s file.' ),
    175175                        '<code>wp-config.php</code>'
     
    178178        <strong>
    179179                <?php
    180                 /* translators: 1: wp-config-sample.php, 2: wp-config.php */
    181180                printf(
     181                        /* translators: 1: wp-config-sample.php, 2: wp-config.php */
    182182                        __( 'If for any reason this automatic file creation doesn&#8217;t work, don&#8217;t worry. All this does is fill in the database information to a configuration file. You may also simply open %1$s in a text editor, fill in your information, and save it as %2$s.' ),
    183183                        '<code>wp-config-sample.php</code>',
     
    187187        </strong>
    188188                <?php
    189                 /* translators: %s: Documentation URL */
    190189                printf(
     190                        /* translators: %s: Documentation URL */
    191191                        __( 'Need more help? <a href="%s">We got it</a>.' ),
    192192                        __( 'https://wordpress.org/support/article/editing-wp-config-php/' )
Note: See TracChangeset for help on using the changeset viewer.