Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Alex Lion (阿力獅)

    (@alexclassroom)

    Hi,

    It’s me again.

    If possible, please implement the following modifications for your plugin’s text-domain.
    https://upload.cc/i1/2020/12/29/BZH6NR.png

    Plugin Author Marios Alexandrou

    (@marios-alexandrou)

    This is now done. If you see anything that doesn’t look right, please let me know.

    Thread Starter Alex Lion (阿力獅)

    (@alexclassroom)

    Hi Marios,
    ultimate-category-excluder.php line 10 should be ultimate-category-excluder, not UCE.
    The current plugin main L10N project is not updated automatically, and I think the wrong text-domain in the file header is the main reason.

    For example, this plugin’s zh_TW L10N project is not automatically updated and still remained old strings.

    Correcting the text-domain in the file header may resolve this.

    Regards,
    Alex Lion

    Plugin Author Marios Alexandrou

    (@marios-alexandrou)

    Thanks again. The text domain value has been updated.

    Thread Starter Alex Lion (阿力獅)

    (@alexclassroom)

    Hi Marios,

    The L10N problem seems to be resolved by correcting the text-domain in the file header.

    This plugin’s L10N project is updated automatically, and I also update the zh_TW sub-project.

    The GlotPress system now pushes this plugin’s zh_TW language pack to WordPress sites setup zh_TW.

    This also means if this plugin’s other language packs are done, the GlotPress pushes them to related WordPress sites, and you don’t need to package them to your plugin’s installation file.

    For example, yes, you don’t need to pack to your plugin’s installation file.

    Your plugins are small, light, and useful, hope they are all L10N ready.

    Regards,

    Alex Lion

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Text Domain Issue’ is closed to new replies.