Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem: Allow ICL_STRING_TRANSLATION_DYNAMIC_CONTEXT to be overriden Solution: This is implemented into String Translation 3.0.10.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by desireeM 1 year, 4 months ago.

Assigned support staff: Bruno Kos.

Author Posts
May 13, 2020 at 8:49 am #6119991

desireeM

"Since these dynamic strings (which are supposed to use this textdomain) obviously cannot have a po/mo (as otherwise they wouldn't be dynamic ), all strings using the "'wpml_string'" text domain will be automatically added to string translation.
This means if a theme or plugin uses this textdomain, we do not have any control over it & it just ends up bloating the string translation with things we do not want to translate (since there's no po/mo available, it would require all manual translations)
By changing the constant value to "custom-dynamic" via wp-config, we can ensure only strings we have created ourselves in our theme will show up dynamically in string translation.

This makes managing strings that ACTUALLY need to be translated harder, since the string translation is bloated with loads of irrelevant strings that need manual translation."

May 13, 2020 at 9:26 am #6120441

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Zagreb (GMT+02:00)

Hi,

According to our developers, it can be done, but can you perhaps give us some ideas how will your project benefit from it?

For what purpose are you using it?

Regards,
Bruno Kos

May 13, 2020 at 9:50 am #6120679

desireeM

Since these dynamic strings (which are supposed to use this textdomain) obviously cannot have a po/mo (as otherwise they wouldn't be dynamic 😉 ), all strings using the "'wpml_string'" text domain will be automatically added to string translation.
This means if a theme or plugin uses this textdomain, we do not have any control over it & it just ends up bloating the string translation with things we do not want to translate (since there's no po/mo available, it would require all manual translations)
By changing the constant value to "custom-dynamic" via wp-config, we can ensure only strings we have created ourselves in our theme will show up dynamically in string translation.

This makes managing strings that ACTUALLY need to be translated harder, since the string translation is bloated with loads of irrelevant strings that need manual translation.

May 14, 2020 at 5:33 am #6128709

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Zagreb (GMT+02:00)

Hi,

Our developers decided to escalate this case and if this gets implemented, I will keep you posted. So there is no need to create a feature request, because internal ticket has already been created.

Regards,
Bruno Kos

May 14, 2020 at 9:42 am #6130655

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Zagreb (GMT+02:00)

Hi,

Your proposed fix is going into String Translation 3.0.10.

Regards,
Bruno Kos

May 18, 2020 at 5:35 pm #6160493

desireeM

Good, waiting for the release in the next weeks.