Task · Languages and translations

Translate with a spreadsheet

Send one language out as a spreadsheet, and bring the finished translations back in.

8 steps · About 10 minutes · Needs: More than one language switched on

  1. Open Translations, pick the language, and select Translator hand-off

    Your eventSet upTranslations

  2. Select Download spreadsheet

    You get a row for everything attendees see in that language. ref names the row, section, item and field say where it belongs in the event, source is your own wording, and translation is the empty column to fill in.

    go.tito.io/acme/summer-fete/admin/translations/ga/handoff

  3. Send the file to whoever is translating it

    They fill in the translation column and send it back. The rest of the file is there to be read.

  4. Select Machine-translate it in Google Sheets first if you want a draft to work from

    It gives you a formula that fills the whole translation column in Google Sheets.

  5. Choose the finished file and select Review the file

  6. Check what the file would change

    New translations, Replacing a translation, Already the same, Left blank and Problems. Every row that would change something is listed below the counts, ticked. Untick any you want to leave out.

  7. Select Import ticked translations

  8. Publish

    Importing saves the wording without publishing it. Attendees read it from the moment you publish.

Good to know

A blank translation cell keeps whatever's already saved.

Ask a translator for twenty rows out of four hundred and the other three hundred and eighty keep the wording they have.

Leave those alone unticks every row that would replace a translation you'd already saved.

Only blank translations get filled in. Include them after all puts them back.

Rows Tito can't act on are listed under Some rows can’t be imported, with the row number and the reason for each. The rest of the file still imports.

  • A row has a translation but no ref, so there's no way to tell what it translates.
  • A ref names nothing in this event. It may have been deleted since you exported the file.
  • A ref names a question from your account's library that this event doesn't ask. Turn on Translate the whole library on the Translations screen and download the spreadsheet again to translate those.
  • A row was translated from wording that has changed since. The reason quotes the wording as it reads today, and you can download the spreadsheet again to translate it.
  • The same ref is on two rows. The one further down the file is imported, and the reason names the row skipped.
References stay the same as your event changes.

A file exported today still imports next week, after rows have moved and new ones have been added around them.

Still stuck?

You can let someone at Tito sign in to your account for a set time, and see every visit they made.

Let Tito support in →