localization - Read For Learn

Localization works but still get “This plugin is not properly prepared for localization” msg in directory

I figured it out almost immediately after asking the question, after months of frustration. The issue was I was using the load_textdomain function (which was the way I learned it) instead of the apparently newer/favored load_plugin_textdomain. The working code looks like this function rsvpmaker_load_plugin_textdomain() { load_plugin_textdomain( ‘rsvpmaker’, FALSE, basename( dirname( __FILE__ ) ) . ‘/translations/’ … Read more

Problems with localization

1) Presuming you’re running WordPress 4.x. The WPLANG constant does nothing. WordPress 3 and below defined the default language in wp-config.php but since WordPress 4 setting your site language is done via the General Settings page in your admin area. Go to Settings > General and scroll to the bottom where is says “Site Language” … Read more

How to detect if text domain is already loaded?

I have to admit that I didb’t understand the setup ;), but it doesn’t matter as the lower level functions (load_textdomain IIRC) will check if a translation file is already loaded and will not load it again, therefor you can use the same file to include many translations, and call the loading function as many … Read more

Alphabetical sorting – local language

I managed to make it work: In wpconfig.php file I set define(‘DB_COLLATE’, ‘utf8_croatian_ci’); Do an SQL query on database in PhpMyadmin with: ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8 COLLATE utf8_croatian_ci I tried setting with utf8_unicode_ci first, sorting was slightly better but not quite accurate.

Localizing strings that come from outside of plugin?

Should such messages be localized at all or are they out of scope for localization? Yes, they should be localized … but don’t depend on the text returned by the API. Does something like __( $message ); even make sense? Not really. First of all, you’re not providing a text domain for the string to … Read more

Shortcodes, output buffering, and WordPress functions

Should I just bring these forms out into templates instead? It depends on the form, and you haven’t printed much detail about what your forms do. Shortcodes are nice but are not the right tool for every job. I would: Prefer a dedicated template to a shortcode, especially for long forms. You start to get … Read more

Internationalization and the plugin description

You need to be using WP’s own tools (makepot.php) for creating POT files for header to be properly scanned and included, see Generating a POT file in Codex. For plugin details to be translated when inactive its header should include properly set up text domain and path to translations folder (if necessary).

WordPress i18n-friendly preg_replace post title

We can use the protected_title_format and private_title_format filters, available since WordPress version 2.8: add_filter( ‘protected_title_format’, ‘wpse_pure_title’, 10, 2 ); add_filter( ‘private_title_format’, ‘wpse_pure_title’, 10, 2 ); function wpse_pure_title( $format, \WP_Post $post ) { return ‘mycpt’ === get_post_type( $post ) ? ‘%s’ : $format; } to get rid of the “Private:” and “Protected:” parts on the front-end … Read more

Difference between 2 internationalization (i18n) functions __() & _e()

__() “Retrieves the translated string from the translate() function” without echoing. _e() does the same thing but echos the output. For more information, take a look at these help articles: Internationalization Localization How to Internationalize Your Plugin Internationalization Security

What are the most used WordPress localization?

tl;dr Usually you should be safe by offering your Plugins in English first. If you create a good userbase, you could do your own resarch as to find out which languages are most important to your clients. Another thing to consider would be, if you want to support latin-signs only or if you want to … Read more

+ More