It is only a design for one site and won’t be a theme anyone can use and hence I don’t want to bother with internationalization. If the theme will only ever be used by you, internationalization isn’t a huge deal. Unless, of course, you will want to use a different language version of your theme … Read more
The translation strings not only get parsed during rendering (output on screen/in browser), but also by the GNU gettext parser. This one is not a PHP parser, so it can’t fetch variables. This is the only part of a Theme or a Plugin, where you need to repeat yourself and add the plain string to … Read more
there is no need to separate code from translatable labels. your plug_get_labels function suffers from the following issues Translation tools can show you the context in which the label is being used which helps in making a good translation faster. With your function you lose context. the use of such function encourage you to call … Read more
The makepot code being used on WordPress.org is a slightly older version that we have not updated yet, specifically with this fix: https://core.trac.wordpress.org/ticket/25665 Basically, it’s only looking in stripe.php for your main plugin lines, not searching for and then finding stripe-checkout.php. This was fixed in the developer tools 7 weeks ago: https://core.trac.wordpress.org/changeset/27399 But the change … Read more
It is because you need to enqueue comment-reply.js which is required for the jQuery effect. Place the following in your header.php file within your head tag: if ( is_singular() && get_option( ‘thread_comments’ ) ) wp_enqueue_script( ‘comment-reply’ );
Before I start, you should never ever use extract(). It is unreliable, and extremely hard to debug when it fails. For this specific reasons, it was (almost) completely removed from core and the codex. For more complete details, see trac ticket 22400. Along with query_posts, these are the two most commonly used and two worst … Read more
Looking at this again, I finally saw it: $clgs_settings_descriptions is defined globally, during plugin load. The textdomain is loaded at action hook plugins_loaded, which is obviously later…
It is possible, and in some cases make sense, but I would advice against thinking that way. Some words in the context of wordpress core admin might be translated differently in the context of a theme. If the motivation here is to save translation time, then don’t bother as any one with translation experience will … Read more
You can set the site language to whatever you wish in the Settings > General > Site Language. After that, you can head over to your profile and choose a language for the back-end. To do so, head over to Users > Your Profile > Language and change it to English. However, there is an … Read more
Always escape output unless you have a great reason not to. The main thing that you lose when escaping translated strings is the ability to use html tags and html entities in the original string and translations, but you should probably not get into a situation in which translators are required to know html just … Read more