The Sendwithus translation feature provides an efficient way to manage localized content. This feature will not automatically translate your templates for you, instead it provides a workflow that allows you to update all localizations of your templates at the same time.

1) Mark-up the templates you want to translate.

Wrap any strings that you want translated with {% trans %} and {% endtrans %} markers. These strings will be pulled out exactly as you mark them, so make sure they are correct.

Markup Trans Jinja Tags

Note: Sendwithus doesn’t support Jinja’s gettext() call.

Using variables in trans tags

Variable assignment and nested variables cannot be used in trans tags. Use Jinja’s set assignment before your translation tag to assign a top level variable to your nested variable.

{% set name = company.employee.firstName %}
{% trans %}Hi {{ name }}{% endtrans %}

For more information visit Jinja Variable Assignments.

2) Download the .pot file

Assign a tag to the templates you have marked up with the “translate” markers. This can be done on the Templates page.

Assigning Trans Tags

On the Manual Translations page, input the tag you assigned into the “Select a tag:” box and click Download POT. This will trigger the download of the POT file that contains all of the strings you will be translating.

Download .POT file

3) Create your translated .po files

For each language you want to translate to, save a copy of the .pot file named after the appropriate language code, with a .po extension (“en-US.po”, “fr-FR.po” etc.).

.PO files

Fill out each of these .po files with the correct translations. Each “msgid” will be replaced with whatever you provide in the matching “msgstr” field.

.PO files

4) Upload the zip file

When all of your .po files are completed, compress them into a .zip file with a name of your choosing. Then re-select tag chosen in step 1 from the PO “Select a Tag:” box, and upload your zip file to generate your localized content.

5) Done!

A locale for each of your .po files will be updated automatically for each tagged template. Check out your template list to make sure things look as expected!

.PO files

If you have any additional questions, feel free to contact us at