I’m guessing that you are using language tags around ‘polish textdeutschland text’ i.e. <!–:pl–>polish text<!–:–><!–:de–>deutschland text<!–:–> but that they got ignored when you posted your answer. I’m pretty sure what you need to be doing is using the __() (which returns the translation for use in php code) and _e() (echo’s direct to screen) wordpress … Read more
You can make changes to the translation, yes, but it’s not as simple as editing the text inside the fi.po file (or any PO file, for that matter). That’s because WordPress actually uses another file, with an .MO extension, to render the translations. That extension is not meant to be read by humans, so you … Read more
Try the following. This is given that the original page url has a .html in it (contact.html and info.html) <li><a href=”https://wordpress.stackexchange.com/questions/87146/<?php if (false !== strpos(strtolower($_SERVER[“REQUEST_URI’]), ‘.html’)) { $uri = str_replace(‘.html’, ‘-ar.html’, strtolower($_SERVER[‘REQUEST_URI’])); } else { $uri = ”; } echo home_url($uri); ?>”>arabic</a></li>
Good question . Well.. After reading Rcalleja answer .. You can use the plugin provided , but there is really no need for it, nor for code hacking or php juggling .. All you have to do is to use the quicktags in the attachments fields : [:en]English Description[:fr]French description[:de]German description After that ( and … Read more
WP translation functions, are meant to translate static strings. E.g. Regarding options, you should use them to translate the labels, not values. However, as far I remember, the translation utility of WPML works in contrast to standard translation, i.e. if you use that than you can’t load the transaltion using from .po/.mo files. If users … Read more
I’m not completely sure whether this is what you want, but if the option page is in one language you can simply put the gettext call in the custom field itself to avoid using variables. For the admin you force the translation to spanish: function wpse227983_force_language ( $locale ) { if ( is_admin() ) { … Read more
The translations hosted in wordpress.org are reviewed and approved by translation validators. Translation validators are recognized with a badge in the user profile. Once approved, the language package is available to be automatically downloaded and installed in any WordPress installation according with its language configuration.
Solved by adding if ( isset( $_POST[‘language’] ) ) { // Input var okay. add_filter( ‘locale’, ‘mbd_set_my_locale’ ); /** * Set locale based on the $_POST choice. * * @param string $locale Locale code. * @return string Selected locale code. */ function mbd_set_my_locale( $locale ) { $language = sanitize_text_field( wp_unslash( $_POST[‘language’] ) ); // Input … Read more
I’m not 100% sure this is the only issue that was preventing POEdit from correctly parsing my code (I’m not sure it actually cares about the WordPress side of things), but fixing these (stupid) errors and re-running POEdit from the .pot file below seems to have generated the correct translation strings: define( ‘MY_TEXTDOMAIN’, ‘MY_TEXTDOMAIN’ ); … Read more
Plugins and themes pull the translation files manually from (mostly) their directory. There are 2 different functions which handle this: For plugins : load_plugin_textdomain() For themes: load_theme_textdomain() The syntax would be something like this, mostly hooked into init or plugins_loaded action hook: load_plugin_textdomain( ‘text-domain’, get_template_directory() . ‘/some-directory’ ); OR: load_plugin_textdomain( ‘text-domain’, false, basename(dirname(__FILE__)).’/some-directory’); Look for … Read more