Translation plugin name

  • Resolved hupe13

    (@hupe13)


    4 months, 4 weeks ago

    I get a warning about mismatched_plugin_name in readme.md:

    Plugin name “(plugin name english)” is different from the name declared in plugin header “(plugin name german)”.

    My website is running in German and the plugin name I translated on Translating WordPress. Is it allowed to translate the plugin name? There are many plugins with translated names.

    If it is allowed, the warning is not necessary.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author David Perez

    (@davidperez)

    Hello,

    Yes it can be translated, but this check is telling you that it has to be the same name in readme and plugin header. So put the same, and then translate it in translate.www.ads-software.com.

    Thread Starter hupe13

    (@hupe13)

    It is the same english name in plugin header and in readme. But the name from readme is translated, because my website is in german.

    Plugin Author David Perez

    (@davidperez)

    Hello, if it’s exactly the same, there is no problem. Share the code to give more context.

    Thread Starter hupe13

    (@hupe13)

    Sorry about the late answer, I was offline last weeks. Result from Plugin Check:

    DATEI: readme.md
    Zeile 	Spalte 	Typ 	Code 	Hinweis 	Link bearbeiten
    0 	0 	WARNING 	mismatched_plugin_name 	Plugin name "DSGVO snippet for Leaflet Map and its Extensions" is different from the name declared in plugin header "DSGVO Snippet für Leaflet Map und seine Extensions".

    First line readme.md:

    # DSGVO snippet for Leaflet Map and its Extensions

    Plugin Name in dsgvo-leaflet-map.php:

     * Plugin Name:       DSGVO snippet for Leaflet Map and its Extensions

    Translated string “Plugin Name: DSGVO snippet for Leaflet Map and its Extensions”:

    DSGVO Snippet für Leaflet Map und seine Extensions

    The warning is therefore not necessary.

    Plugin Author David Perez

    (@davidperez)

    I understand clearly this issue. This bug was flagged also by Rod-Gomez in GitHub:

    https://github.com/WordPress/plugin-check/issues/764

    And it’s solved and planned to be launched very soon in version 1.3.0

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.