While it is preferred to speak in English or use a human translator whenever possible, sometimes machine translation is necessary.
When a client’s primary language is not English, MechaSqueak provides integrated translation capabilities that allow dispatchers to translate without resorting to external tools.
When a case comes in, the "case language" will be set to the preferred language setting of the client's web browser. If the language setting does not match what the client is speaking, you must change the language of the case for translation tools to work correctly.
!lang <language-code> |
You can find a list of supported languages for translation here with their language code.
If the language remains at en, MechaSqueak will assume translation is unnecessary.
To view an English rendition of the client’s messages in real time, activate live subtitles:
!tsub notice # translations delivered as IRC notices (recommended) |
A translated message will appear in IRC under the original message like this:
<spacedawg> отправил запрос дружбы |
Notices appear in the active channel window but are visible only to the subscribing dispatcher. Should your IRC client handle notices poorly, private‑message delivery is available:
!tsub pm # translations delivered via private message |
The subscription persists until explicitly cancelled:
!tunsub # terminate the subscription |
Live translations for the client remain active even after the case has been formally closed until the case number is re-used by a new case. When a new case is assigned to the number, Mecha will 'forget' the old client.
The /tr slash command allows translation to be provided by mecha while posting under the dispatcher’s own nickname, preserving the natural flow of conversation.
/tr <case‑id> <message> |
Example :
/tr 4 Please drop out of supercruise |
When the dispatch uses this command, Mecha will send the original english message to anyone else currently subscribing to translations via !tsub so rats and other dispatchers are aware of what is being said. Dispatch messages are not translated if they are typing in a foreign language themselves or using an external translation tool.
Sometimes you may need to send a translated message in the channel to someone without a case ID, the /tr command allows you to define a target channel and language.
/tr <channel> <language‑code> <message> |
Example:
/tr #fuelrats es Frame shift complete; slowing to sub‑light. |
Prerequisite: The IRC client must allow the transmission of raw text lines. HexChat, WeeChat and Polaris meet this requirement; certain web clients do not. Some clients like IRSSI may require you to change a setting or add your own alias to make it work.
Althrough /tr is recommended, there are also regular !commands that can be used in the channel or in a PM with MechaSqueak in situations where IRC server /commands cannot be used.
Objective | Slash Method | Bot Alternative |
Send a translated message to the client | /tr <case> <text> | !tc <case> <text> |
Translate English → target language, display result only | – | !t‑<code> <text> |
Translate and transmit to a channel as the dispatcher | /tr <chan> <code> <text> | !tme <chan> <code> <text> |
More information about these Mecha commands is available on the Mecha help page
Executing !grab on a message written in a foreign language automatically stores an English translation alongside the original text.
What service do you use to perform machine translations?
Are these translations reliable?
Why did you choose to use GPT for translations?