Translations

Hinsley supports translations of forecasting questions and contributor text on forecaster networks. Question translations can be generated and edited in the question form. Comments and forecast rationales can be translated automatically when that option is enabled for the network.

Available Languages

A published question offers the combined languages enabled on every network where it is published. Its source language is excluded from the translation targets. British English uses the English translation. Language tabs appear only when at least one target language is available, so a new, unpublished question has no translation tabs.

Network Settings

Translating a Question

The question form includes translations for the question wording, short name, saved answer names, background information, and resolution criteria. Save newly added answers before translating them. Dates and other question settings stay on the source tab.

Open Edit question on the network, or edit the question in the analyst workspace. Your usual question-editing permissions apply.
Select a target-language tab. Each field shows its source text above the translation input.
Choose Translate all to fill missing, out-of-date, and failed translations in that language. Current translations and translations edited by an admin are kept.
When the run finishes, the results appear in the form and are already saved. You can review and correct each field.

After editing, choose Save once to save changes across all language tabs. Clearing a translation removes it. Translate buttons are disabled while the form has unsaved changes; save before starting a run.

Choose Translate this field for one missing translation. Translate again replaces that field's translation, including an admin's correction.

The Source Language

The first tab contains the source text, even when your own interface uses another language. The Written in setting identifies the language the question is written in. The other tabs contain translations of that source.

Changing the source-language setting keeps the source wording and changes which language it belongs to. It does not translate that wording. Existing translations of the question, its answers, and its clarifications become out of date and need updating.

Translating Clarifications

Save a new clarification first, then open its edit form. It has the same source and target-language tabs as its question. On a target tab, choose Translate this field or Translate again, or enter a translation and save. Clarifications use the question's source language.

Translation States and Source Changes

Missing: No translation is stored for this field and language.
Translating: A translation run is in progress. The fields it covers are temporarily disabled.
Current: A machine translation is available for the current source text.
Edited by admin: An admin saved a translation. Translate all preserves it while its source is unchanged.
Out of date: The source changed. The previous translation remains in the form for editing, while readers see the source.
Failed: Translation did not complete successfully. You can try again or enter a translation by hand.

Editing a source field makes its existing translations out of date. Readers see the updated source until those translations are updated. If you edit the source and a translation together in the same save, that translation is saved against the new source.

If someone changes the source after you open the form, saving a translation shows an error and keeps your entered text. Check the updated source before saving again. If a translation run finishes while you have unsaved changes, the form keeps your edits and displays a notice to save and reopen it to see the results.

Machine translation uses the account's AI budget. If the monthly budget has been used, the form displays a notice and machine translation is unavailable until the next billing period. You can still enter and edit question translations by hand.

Automatic Translation of Contributor Text

Automatic translation of contributor text is off by default. Contact the Cultivate Labs team to enable it for a network with more than one language. This setting is separate from the question translation controls described above.

New and edited contributor forecast rationales and comments on questions, forecasts, forum threads, and blog posts are translated into the network's other enabled languages. Hinsley detects the language of the text. Forum titles, blog article bodies, and email bodies are outside this automatic translation feature.

Enabling automatic translation does not translate existing posts. When an author edits their text, previous translations are removed and new ones are requested. These translations have no manual editing form. Disabling automatic translation stops new automatic translations; existing translations remain available.

What Readers See

Readers see available translations in their selected language. Translated comments and rationales include a Translated from label and a Show original control. Choose Show translation to switch back. These controls also appear on translated comments in the activity feed.

If a translation is unavailable, still being generated, or has failed, readers see the source text. A recently posted comment or rationale may display Translating. Question fields whose translations are out of date also show their source text until a translation is updated.

Hinsley Documentation