wp_localize_script() defines a variable in the global JS scope – in the case of your code, the object is placed in a globally-scoped variable with the identifier MediaFolders. In your load event callback you are also defining a variable with the identifier MediaFolders scoped to it’s encapsulating function body – so when you use the … Read more
check out the automattic themes svn repository which holds about 108 that all should be internationalization (big word) ready https://wpcom-themes.svn.automattic.com/
take a look at qTranslate Main features: qTranslate Services – Professional human and automated machine translation with two clicks One-Click-Switching between the languages – Change the language as easy as switching between Visual and HTML Language customizations without changing the .mo files – Use Quick-Tags instead for easy localization Multilingual dates out of the box … Read more
Use the CS Localization plugin and generate the po/mo files, thats all. Save the file also in the repo of git and ready. The performance of the theme is not so high, if you have the strings inside the php-files, but only so it is possible to create different languages for the themes. mo/po files … Read more
Sure, the gettext filter does exactly what you require. Here’s some code that should work out of the box: function wpse31449_translate_my_stuff($translation, $text, $domain) { if ($text == ‘Featured Image’) return ‘Post Image’; return $translation; } add_filter( ‘gettext’, ‘wpse31449_translate_my_stuff’, null, 3 ); Note: if the translation is retrieved with a gettext context (_x() and _ex()) then … Read more
Use the __() function, just as you see in the the_content() example: <?php echo get_the_term_list( // ID $post->ID, // taxonomy ‘book’, // Before __( ‘Books: ‘, ‘ft’ ), // Separator, see http://core.trac.wordpress.org/ticket/7897 __( ‘, ‘ ), // After ‘ ‘, // Looks like you’ve added an extra parameter? ” ); ?> Note 1: I split … Read more
You cannot translate text you don’t know. The translator must know the text before it was submitted – impossible. The only solution is: add all language strings manually for each sub site.
Well use translation plugin (multilingual Plugins)to create page in english and gujrati. There are a few basic types of multilingual Plugins: 1 Manage multilingual posts in one post per language (e.g. WPML – paid, xili-language, Polylang or Bogo). Translations are then linked together, indicating that one page is the translation of another. 2 Store all … Read more
If these theme strings are prepared for translation and the theme is not in english by default (they’re outputed with __() or _e() functions) and you include your theme textdomain correctly, then you probably haven’t translated these strings to english. WPML had/has some tool to do this, but it isn’t very user-friendly (at least I … Read more
The correct string is ‘← Back to %s’. The site name is inserted after the translation. See the function login_footer() for details.