Romanian to German, with your vocabulary intact
In a plant briefing the hard part is never the grammar. It is that your line, your part number and your internal process have names, and a translation that invents new ones for them is worse than no translation. A glossary you write once fixes them, and every session after that uses your wording.
The words that matter are yours, not the dictionary's
A glossary entry is one term with a rendering for each output language you offer — so an entry only reaches German if you gave it a German rendering, and a term you filed but left blank there simply is not used. Up to a hundred entries, each term up to eighty characters. The model reads them when a translation session opens and keeps them for that session's life, which is why they go in before you start rather than in the middle of a shift briefing.
- Up to 100 glossary entries, each with a German rendering
- Scripture from the Luther Bible, on a worship account
- Audio straight from the desk or an encoder
- A recording of the whole session, if you switch it on
- Glossary entries
- 100
- Term length
- 80 characters
- Bible translation named
- Lutherbibel
- Free on signup
- 30 credits
Where Romanian to German comes up
Mostly at work, and once a week in a hall.
Shift briefings and safety instruction
One voice to a room, which is the case this handles best. Put the process names in the glossary and they come out the same in every briefing rather than differently each time.
Audits and visits from headquarters
Feed the same audio your PA already carries, from the desk or from an encoder. In encoder mode the broadcast belongs to the session rather than a browser tab, so it survives somebody closing the laptop.
Congregations with German ties
A quoted verse is rendered in Lutherbibel wording rather than freshly translated from the Romanian, which is what makes a familiar passage land as familiar.
Common questions
How do we stop it inventing names for our parts and processes?
The glossary. One entry per term, with the German rendering you want, up to a hundred entries. An entry with no German rendering does not reach German at all, so filling it in is the step people forget. The model reads the glossary when a session opens and keeps it for that session, so edits reach the next session and not the one already running.
Can we keep a recording of a safety briefing?
Yes, as a separate switch: the spoken track and one translated language are saved, with a bar showing where speech and pauses were. It is the one setting that spends credits even with nobody listening, because the translation has to keep running to be recorded — the console flags the cost beside the switch. Whether a recording satisfies a legal record is a question for whoever advises you, not for us.
Is this good enough for a works council or a legal matter?
For understanding a briefing, yes. For anything where a mistranslation has legal weight — a disciplinary hearing, a contract discussion, a formal consultation — put a professional interpreter on it. You can do that on the same broadcast: any output language can be handed to a person, and the AI keeps the rest.
Does the second shift cost the same as the first?
It costs what it uses. A language is metered only while somebody is listening to it, so a briefing nobody joined in German is not charged for German. Each listener adds a small amount on top, so a shift with thirty people does cost visibly more than one with three — but the translation itself is done once however many join, and that part does not move. Credits do not expire, so a quiet month costs nothing.
Try it on one shift briefing
30 free credits, no card. Long enough to see how your own terms come out.