You should use a localized XML format like XLIFF or TMX , there is a tool to convert XLIFF to .po. If you cannot change the source XML you have a few options but it really depends how your outputting this XML info: Parse the XML ( for label) and create a .po with gettext … Read more
The second part is not required, it just loads a PHP file with language specific functions. Examples In some countries/regions/religions it is not allowed to use capital letters in a word for anything else than the name of some god. In these cases you probably want to remove the WordPress to WordPress filter. Some languages … Read more
In your theme, you enqueue the stylesheet usually like this: add_action( ‘wp_enqueue_scripts’, ‘t5_enqueue_style’ ); function t5_enqueue_style() { wp_enqueue_style( ‘theme-name-default’, get_template_directory_uri() . ‘/css/default.min.css’ ); } The extra RTL stylesheet is enqueued here too, listing the default as dependency: if ( is_rtl() ) { wp_enqueue_style( ‘theme-name-rtl’, get_template_directory_uri() . ‘/css/rtl.min.css’, array ( ‘theme-name-default’ ) ); } So the … Read more
No, it is not. Use esc_html__( ‘string’, ‘text_domain’ ) instead (two underscores). Translated strings are unknown input. Unknown input is per default malicious. You don’t know where the language file comes from. It doesn’t even have to be the one you provided, because the path can be filtered or changed with a symlink. Even if … Read more
(I revised this answer mainly to let other readers and you know the issues I originally noticed in your steps as shown in the question.) So in my original answer, I was focused on suggesting you to just go with the multiple script translation files, but I thought I should clarify the three things below: … Read more
you may use this below code for your problem: [1]: https://i.stack.imgur.com/5aX1D.png or use below code: add_action( ‘after_setup_theme’, function () { load_theme_textdomain( ‘your parent theme name’, get_stylesheet_directory() . ‘/languages/’ ); load_child_theme_textdomain( ‘your child theme name’, get_stylesheet_directory() . ‘/languages’ ); } );
You can’t do that, at least not from a GUI translation helper app, because these are set to pick up strings from standard functions like __(), _e etc, they can’t read variables (including string variables) Instead try: var $control_types = array( array( ‘key’ => ‘manual’, ‘value’ => __(‘Manual’, ‘yourtextdomain’) ) ); But if $control_types is … Read more
I’m not really up to date on WPML and how it handles translations, but my general understanding is that in most cases it simply creates duplicate entries for each language and links them together with the “original”. However, I recently hade a similar problem where I needed the ability to add a “pluralized” version of … Read more
Filter template_include: add_filter( ‘template_include’, ‘prefix_translate_template’ ); function prefix_translate_template( $template ) { if ( ‘category-‘ . __( ‘news’, ‘your_textdomain’ ) . ‘.php’ === $template ) return ‘category-news.php’; return $template; } But I think templates based on slugs are not a good idea in that case.
esc_html_e() and esc_attr_e() are merely wrapper functions for _ to save a little bit of typing and help with readability. You’re right, there isn’t one for _n, so you’ll just need to do the “wrapping” yourself: printf( esc_attr( _n( ‘%s item’, ‘%s items’, $count, ‘textdomain’ ) ), number_format_i18n( $count ) );