• Resolved samicai

    (@samicai)


    I want to translate only dynamic content, not posts or other static content.

    Many plugins already provide translation files such as .po files, so these strings do not need to be translated manually.

    TranslatePress does not seem to provide any option to import or manage translation files.

    Why is this functionality not included? Being able to use existing plugin translations would be very important and useful, since many plugins already ship with translation files.

    Is there any possible workaround to use existing plugin translations as long as importing translation files is not supported?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Iarina

    (@iarinadasdi)

    Hello @samicai,

    Thank you for your message!

    We have a setting that addresses exactly what you are describing. Under TranslatePress Settings → Advanced → Debug tab, you will find the “Disable translation for gettext strings” option. When this is enabled, TranslatePress will no longer process strings that come from plugins or themes, and those strings will instead be served directly from their existing po/mo translation files.

    The only thing worth keeping in mind is that with this option enabled, you will no longer be able to edit gettext strings through the TranslatePress editor or use automatic translation on them, but since you mentioned those strings do not need manual translation anyway, that should not be a concern for you.

    Thread Starter samicai

    (@samicai)

    I tried your suggestion and it worked perfectly.

    I appreciate your help and quick response.

    Best regards

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.