Sending copy to a translation vendor, and bringing it back

Translation work happens outside this console — a bureau, a bilingual staff member, or the community organization that actually speaks the language your fifth language needs. This screen is the round trip that gets your copy to them and their work safely back.

Exporting

Choose whether to export only the keys currently missing a translation, or every key you have. The file itself is built specifically for spreadsheet tools to open correctly — UTF-8 with the byte-order mark and line endings a translator's software expects, so Hebrew and Arabic text doesn't arrive garbled the moment someone opens it.

Importing is always a preview, never a direct write

Whether you upload a file or paste CSV text directly, nothing is saved yet. The screen parses it, matches every row against your real catalogue, and shows you a change list — this key, this language, from this text to that text — with the previous value struck through so you can see exactly what would change before anything does.

What gets flagged before you apply anything

A row naming a key your catalogue doesn't recognize, or a language your organization hasn't enabled, is called out by count rather than silently skipped or silently applied. Read those two numbers before you click apply — they're usually a sign the vendor's copy of your export is out of date, not that your export was wrong.

Applying

One button applies every change in the list at once. There's no per-row approval — by the time you're looking at the change list, you've already decided this file's answers are the ones you want; the preview step was the actual decision point, and applying is just carrying it out.