Support

February 1, 2019 at 7:02 am

Hi,

Here’s the string in the source:

https://github.com/eventespresso/event-espresso-core/blob/master/modules/single_page_checkout/reg_steps/attendee_information/EE_SPCO_Reg_Step_Attendee_Information.class.php#L298

You’ll note that the translation function used there is esc_html_x(), which unlike many of the other translation-ready strings in EE4. You could check to see if loco translate requires doing something different for translating when the translation function is esc_html_x().

February 1, 2019 at 2:02 pm

You’ve edited the PHP files directly? If so that’s not the correct method to translate the plugin and you’ll lose any changes when Event Espresso updates.

You can just translate the Attendee %d string to change the above.

February 4, 2019 at 2:35 pm

Hi,

One way to translate the above string would be to use the gettext_with_context filter. Here’s a code example that shows how to use that filter to translate that string:

https://gist.github.com/joshfeck/62183600028f7ff7bd135bfdc89c5684
You can add the above to a functions plugin or, if available, into your WordPress child theme’s functions.php file.

February 5, 2019 at 5:41 am

But it would be nice, if the problem would be fixed in general.

Please explain what exactly “the problem” is. The text is translation-ready. For example, if another plugin is unable to translate that string, the fix will need to happen in the other plugin.

February 5, 2019 at 9:18 am

May I ask which po file are you using, and where was it downloaded from?

February 8, 2019 at 10:35 am

It doesn’t appear that the string is translated:

https://slack-files.com/T02SY781D-FG22GHKSP-9f70a143f5

I can add one now so if you do another export the .mo file will include a translation for that string.