It seems that you’re adding translatable strings with text domain “custom-strings” but loading a text domain “Divi” in load_child_theme_textdomain. Needs to be the same Don’t use the same text domain as your parent theme. If your parent theme is Divi, use divi-child (it should match your child theme slug). In your child theme’s style.css, define … Read more
Your error (actually a warning) seems to come from the Theme Check plugin. There’s nothing wrong with the code you’re showing above. ‘acf’ is your text domain. and the _n function takes four arguments as you’ve given it. It strikes me that the Theme Check plugin is not very good at static analysis of function … Read more
so you will need at least translations into german. there shouldn’t be other packages loaded for your site. you can find these files in the language folders in wp-content. there are other language folders as well in the plugins or in thmemes.
No, there isn’t. The text domain needs to be hard coded, otherwise it can’t be read by localization tools which parse the code without executing it. See this note from the Internationalization documentation The text domain should be passed as a string to the localization functions instead of a variable. It allows parsing tools to … Read more
Your first line of code looks ok, are you sure you have a translation for the ‘Featured’ string in your PO file? Your second issue is an excellent example of how you should not use the gettext functions. You are trying to translate dynamic string ‘<a class=”more-link” href=”‘. get_permalink($post->ID) . ‘”>Read More</a>’ for which you … Read more
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
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
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
I’d use printf to put the markup into place after the translation. You can force the order with the right modifiers, but translators are probably smart enough to not really need that. printf( __(‘The image %sMUST%s be less than %s500 KB%s in size.’, CUSTOM_TEXT_DOMAIN), ‘<em>’, ‘</em>’, ‘<strong>’, ‘</strong>’ ) ; I consider Otto’s post to … Read more