fr, en, sw, pt-BR.
Each subscriber’s language
A subscriber’s language arrives through:
- their record, in the interface;
- the subscription form (the
localefield); - an import (a langue, language, lang or locale column, as a code or a name:
fr,Français,French); - the API (
locale); - their preferences page, where they choose it themselves.
Writing a translated version
Above the editor of a campaign, an automation e-mail or a transactional template, the language tabs:1
The base version
The first tab is the base version, in the list’s language. It is what
anyone whose language has no version receives.
2
Add a language
Add a language, type a few letters (“span”, “swah”), choose. A tab
appears.
3
Write the translation
In the tab, the subject and the content belong to that
language; the preview shows them with the matching
lang attribute.
The template, the editor and the settings are shared by every version.4
Save
Save saves every version at once. A version left entirely empty is
not kept; the cross on a tab removes the language.
Who gets what
For each subscriber, Lekalao takes:- the version of their exact language (
pt-BR); - failing that, the version of the language without its region (
pt); - failing that, the base version.
<html lang="…"> tag, which helps screen readers and some filters.
Sending to one language
To write to one language only, create a segment with Language is…. “Portuguese” takes inpt and pt-BR; “Portuguese (Brazil)” means pt-BR alone.
The versions of an A/B test are not translated: a campaign in an A/B
test has no language tabs. To test two subjects in two languages, make two
campaigns, each on a language segment.
Transactional e-mails
Your application chooses the language on every send, with thelocale parameter:
locale, the base version goes out. See Transactional e-mails through the API.