The Translations Tab

The Translations tab is the third tab under Events, after Events and Categories. It answers one question: in this language, which of my events still need work? It is a work list, not a to-do list. A missing translation never blocks anything, because players read the original text meanwhile, so it does not belong in your Queue.

Pick a Language

A row of buttons at the top names the languages your events need, for example Swahili. Next to it a line says what your players read, such as "Your players read Swahili or English". Pick a language to see every event in it.

If your operator offers only the language your events are written in, the tab says that no language needs translating yet.

The List

Each row is an open event. It shows:

• the event, with its category and its number of markets,
• the owner: Yours or Platform,
• when it closes,
• the language's bar and counts, such as "3 missing · 2 out of date · 33 waiting for approval",
• Review, and Translate when something is missing or out of date.

The list shows open events, soonest closing first, because that is what players are reading now. Archived events are hidden. It loads more as you scroll.

Filter chips with counts sit above it:

An event waiting for approval is work like a missing one: players read the original for those texts until a person approves them.

Translate Missing for Several Events

Content and Admin staff see a tick box on each row. Tick the events you want. A bar appears: "3 selected", with the estimate, for example "about 3 US cents", the button Translate missing for 57 texts, and Clear. The estimate is shown before you press the button. If nothing is missing in the events you ticked, the bar says "Nothing to translate in these".

Pressing it starts one translation per event, in the language you picked, and says "Translating Swahili for 3 events. Watch it below." Each shows as a progress row above the list, "Translating 41 texts · 12 done · Swahili · 3 events", with Cancel, and your team can watch or cancel it. A row of the list shows "Translating 12 of 41" while its event is being translated. The translations run on the server, so you can leave the page. Drafts arrive as Waiting for approval, and a text a person has saved meanwhile is never overwritten.

The Translate button on a row does the same for that one event.

Review Next

Review next at the bottom of the list opens the review screen on the first event of the list. Finishing one event's review opens the next, so you can work through a language without coming back to the list. See Reviewing Translations.

Phoenix Events on Your Site

By default the list holds your own events. The switch Phoenix events on your site (read only, Report a problem) changes the list to Phoenix's events that your players can see, with Phoenix's coverage in your languages.

• Phoenix writes and translates these events, so the rows have Read and Report a problem instead of Review and Translate, and no tick box. Both open the translations of that event, read only, in that language. On a row, Read and Report a problem open the same screen: press R on a text there to report it. See Reporting a Translation Problem.
• Above the list, Your reports says "what you told Phoenix is wrong, and what Phoenix answered". Each report shows the event and the text ("Swahili title"), the reason, how old it is, and where it stands: "Open, waiting for Phoenix", "Fixed by Phoenix", or "No change needed" with Phoenix's answer. Read opens the text.
• A row shows a badge such as "2 sent by you, open" for each report of yours that Phoenix has not answered yet.
• The filters work as for your own events. For a Phoenix event they tell you how far Phoenix has got, not what your team has to do.

Switch it off to return to your own events.