Context Navigation

← Previous Ticket
Next Ticket →

#4019 closed defect (bug) (fixed)

Gutenfront: Typographical errors

Reported by:	tobifjellner	Owned by:	SergeyBiryukov
Milestone:		Priority:	normal
Component:	General	Keywords:
Cc:

Description (last modified by SergeyBiryukov)

[7995] introduced some typos and typographical errors at https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/themes/pub/gutenberg/gutenfront-content.php?marks=34-37#L34

Currently it reads:

<?php
/* translators: 1: The URL to the Clasic Editor plugin. 2: The URL to the Gutenberg plugin.  */
wp_kses_post( __( 'Gutenberg is available as part of WordPress 5.0 and later. The <a href="%1$s">classic editor</a> plugin allows users to switch back to the previous editor if needed. Future development will continue in the <a href="%2$s">Gutenberg</a> plugin.', 'wporg' ) ),
esc_url( "https://{$localised_domain}/plugins/classic-editor/" ),
esc_url( "https://{$localised_domain}/plugins/gutenberg/" )

In the translators' comment: Clasic Editor -- Classic Editor
In the string itself, the plugin name "Classic Editor" should be capitalized, I believe.

Change History (7)

#1 @dd32
6 years ago

In the translators' comment: Clasic Editor -- Classic Editor
In the string itself, the plugin name "Classic Editor" should be capitalized, I believe.

Well spotted! Both of those typo's existed previous to the above commit. I wasn't sure if the plugin should be called Classic Editor or classic editor in this context, so left it as it was previous.

@azaozz what's your opinion on how to correctly refer to the plugin here?

#2 @azaozz
6 years ago

Right, it's a bit confusing. The plugin's name is "Classic Editor", so when used as a name it should be capitalized (as reported in the ticket).

It's also possible to refer to "WordPress' classic editor" (as type of one of the editors) where it is not the plugin but the old editor. Then IMHO there is no capitalization.