EME by default supports multiple languages for the backend (typically called the “plugin” language, which follows the wordpress language). However, in the case some kind of language plugin is installed to help your site be multi-lingual, things become more difficult. Reason is that the RSVP form, mail templates, event titles, etc … all need to support your languages of choice.
EME tries to detect the used language by checking the url. It supports “https://my.site/?lang=en” format or “https://my.site/en/” format.
When wanting to support multiple languages, EME works very nicely together with qtranslate-xt. But if you’re using another plugin for languages, EME can still help you. You just need to use language tags to indicate the language for a specific part of text. An example for an event title:
[:en]title in english[:de]title in German[:nl]title in Dutch[:]
Or for content of an event (or mail), as an example with sections that are not translated (like a name):
[:en]Hi[:nl]Hallo[:] #_FIRSTNAME,
[:en]Thank you for reserving for[:nl]Bedankt voor uw reservatie voor[:] #_EVENTNAME
When the language is English, this then gets presented as:
Hi #_FIRSTNAME,
Thank you for reserving for #_EVENTNAME
And in Dutch:
Hallo #_FIRSTNAME,
Bedankt voor uw reservatie voor #_EVENTNAME
If a section of text is not enclosed between language tags, it is used in all languages. If no language is detected, or the language of choice is not present in the text, the first language found is used as a “default”.
EME supports both the language tags [:xx]…[:] and {:xx}….{:} (both of which are also used by qtranslate-xt).
EME also follows the language of choice when sending mails to people (as indicated in their EME profile, not WP).