Retrieved menu items pass through wp_get_nav_menu_items filter, as well as few others in wp_get_nav_menu_items() and around. — EDIT – This is what I used: function translate_menu( $items, $menu, $args ) { foreach ( $items as $key => $item ) { $items[$key]->title = _($items[$key]->title); } return $items; }
Stylesheet Printing Order WordPress does not load themes’ alternative rtl.css files using wp_register_style() or wp_enqueue_style(). As such, the stylesheet does not get added to WordPress’s style queue, and cannot be specified as a dependency when registering or enqueueing additional stylesheets. Instead, this stylesheet’s <link> element is added via the locale_stylesheet() function, which is attached to … Read more
There is no technical problem in doing so, and there won’t be any complications or errors. However, it could be that not all content on the site will be in Indonesian. Some strings in themes and in other places in the front-end are outputted by WordPress, and as all strings are in English in WordPress … Read more
While I can’t see any major fault in doing the way I proposed initially especially in relation to translation and localization, what I realised while researching this issue was that I was asking an ajax question. Basically what’s the most efficient method to initialize the I18n components of wordpress. Short of making a custom ajax … Read more
Tweak the loop for translation
You can not translated dynamic strings with he translation API, you can translate only static strings that you know in advance.
OMFG that is the most stupid code I saw in core for some time. Don’t follow the comments there, if you want to use a different flavor of open sans just write a plugin that deregister the style and add the one you want to be used instead function replace_open_sans() { wp_deregister_style(‘open-sans’); wp_register_style(‘open-sans’, ‘http://fonts.googleapis.com/css?family=Open+Sans:300’); wp_enqueue_style(‘open-sans’); … Read more
Ok for everyone else’s benefit this is what is not explained in the documentation: You need to specify a textdomain anyway in your plugin (and together with it the path to the directory containing the language files, as usual). The PHP file used for the translation should contain an array like: $strings = array( ‘string1’ … Read more
Whats a good strategy for localising WordPress post and page content?
Thanks @toscho — The problem plugin in particular is wp-pagenavi. The backend strings are being translated, however; the frontend remains in default en_US locale. I found this: https://wordpress.org/support/topic/translation-91 To be more specific, the text field values on plugin options page do not get translated so my assumption is that translations are malformed somewhere in the … Read more