Internationalization doesn’t recognize strings already translated

  • Hi! I have this plug-in: https://www.ads-software.com/plugins/laika-pedigree-tree/

    I’ve translated it (some strings, others are obsolete). It works. On my page plug-in if I go to translate it recognize the strings, but doesn’t read those that are already translated in my .po files.

    My code is

    * Text Domain: laika-pedigree-tree
* Domain Path: /languages
*/

if ( ! defined( 'ABSPATH' ) ) exit;

function laika_pt_textdomain() {
	load_plugin_textdomain( 'laika-pedigree-tree', false, 'laika-pedigree-tree/languages' );
}

    Is that normal, or WordPress translation page should recognize my strings already translated?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator bcworkz

    (@bcworkz)

    AFAIK, yes. Otherwise, assuming you’d be distributing files to translators, you’d be asking them to translate what has already been done. The various .po files are merged when you compile the .mo file, so fragmented files are not an issue. I don’t have much experience in i18n, but this behavior makes sense IMO.

    Thread Starter burria

    (@burria)

    Thank you @bcworkz, I was a bit confused.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Internationalization doesn’t recognize strings already translated’ is closed to new replies.