Reporting a Translation Problem
Tell Phoenix when a translation of one of its events is wrong, and read its answer on the text
Phoenix writes its own events in English and translates them into the languages operators offer, so your team reads those translations but never edits them. When one is wrong, you report a problem. The report reaches Phoenix staff, and Phoenix's answer comes back to the same text.
A report never changes a text and never changes what your players read. Only Phoenix's own change does. Until then your players read what they read before.
Staff with the Content or Admin role can send reports. Other roles can read them.
Send a Report
Open the Phoenix event in your language
Either open the event page of a Phoenix event, pick one of your languages on the language bar and press the flag beside a text, or press Report a problem in the Languages card. Both open the translations of that event, read only. Or open Events > Translations, switch on Phoenix events on your site, and press Read or Report a problem on its row (see The Translations Tab).
The screen is titled "Swahili of a Phoenix event", for example. It says that Phoenix writes the event and manages its translations, and that you read them as your players get them. It lists only your languages.
Move to the text and press R
Move with J and K, then press R, or press Report a problem on the row. Any text can be reported, whatever its status: a wrong translation, a misspelled one, or a text that is Missing. On an Out of date or Missing text the row says that your players read the English until Phoenix updates it.
Say what is wrong
The dialog "Report a problem with Phoenix's Swahili" names the text and quotes it as players read it. It asks What is wrong:
| Reason | Use it when |
|---|---|
| Wrong meaning | The translation says something different from the English |
| Spelling or wording | The meaning is right but a word, a spelling or a phrase is not |
| Missing text | A text has no translation, or part of it is left out |
| Other | None of these fits. A note is required |
Under Say what it should say, write what the text should read. The note is optional, except for Other, where the field reads "Say what it should say (needed for Other)". The more exact it is, the faster Phoenix can act on it. Send to Phoenix stays disabled until you have picked a reason and, for Other, written a note.
Send to Phoenix
Press Send to Phoenix. A message says "Sent to Phoenix: it is in their Queue and Translations tab. Their answer shows on this text." The report carries your name and your operator's name.
Where You See Your Reports
A sent report waits on Phoenix, so it is not a task for your team and it is not in your Queue. You see it here:
- On the text. A box under the text says "Reported", by your operator, by whom and when, with the reason and your words, and "Waiting for Phoenix. It is in their Queue and Translations tab." until it is answered. Reports from your colleagues show too.
- On the review screen. The filter Your reports lists the texts you have reported, with their count.
- In the Translations tab. With Phoenix events on your site on, the Your reports panel above the list shows each report and where it stands, and an event with open reports of yours carries a badge such as "2 sent by you, open".
Phoenix's Answer
Phoenix staff answer each report in one of two ways. The answer replaces "Waiting for Phoenix" in the box on the text, and shows in the Your reports panel.
| Answer | What it means |
|---|---|
| Fixed | Phoenix changed the text |
| No change needed | Phoenix explains why the text stays as it is, in an answer you can read on the text |
The box then shows "Fixed" or "No change needed", and "Phoenix", the person's name, when, and the answer. An answered report is closed for good. If the text is still wrong, or a new problem appears, send a new report.