Manage translations, your glossary and translation memory

Every translation FluentC makes for your site is managed in one place, the dashboard, whether your languages come from Domains or from the WordPress plugin. Two screens do the work:

• Translations lists every translated line. Search it, change any line by hand, import and export it as CSV.
• Translation Memory is your glossary. Add a term once, with the translation you want, and FluentC uses it across all your sites.

Edit a translation

1. Sign in to the dashboard and open Translations.
2. Choose a site and a language. Search for the original or the translated text, and sort by last updated, original text or translated text.
3. Open the line, change the translation and save.

What you save is what visitors get from then on. The same screen works for every site on your account.

On WordPress, the plugin's Edit Translations menu item opens this screen, so there is nothing to edit inside WordPress itself.

Edit many lines in a spreadsheet

1. On Translations, set the site and language you want, then choose Export current view to CSV.
2. Edit the translated_text column. Leave the id and type columns as they are, because they tell FluentC which line each row is.
3. Choose Import translations from CSV and pick the file. FluentC reports how many lines it saved and which rows it skipped.

Add terms to your glossary

The translation memory is your glossary: a list of terms and phrases, each with the translation you want. Use it for the words that must always come out one way: your brand and product names, the terms your trade uses, a phrase your legal team has approved.

1. On Translations, choose Translation Memory, then Add Entry.
2. Pick the source language and the target language. An entry belongs to one language pair, so add one per language you translate into.
3. Enter the source text and the translation you want.
4. Add a note if the AI needs context, such as "product name, keep in English". Notes are passed to the AI along with the entry.
5. Save. The entry is Active and used the next time FluentC translates text that contains it.

To add many entries at once, switch on Bulk Entry Mode and paste the source texts and the translations as two matching lists, one per line.

Manage entries

• Edit an entry to change its translation or note.
• Deactivate an entry to stop using it without deleting it. Inactive entries are ignored. Activate brings it back.
• Delete removes it.
• Filter by source language, target language and status, or search the source and target text.

Import and export entries as CSV

Export current filters to CSV downloads the entries you are looking at. The columns are id, source_language, target_language, source_text, target_text, active and notes. Import entries from CSV reads the same columns: a row with an id updates that entry, and a row without one creates a new entry.

How the glossary is used

• It is company-wide. Entries belong to your account, not to one site, so a term set once is used on every site, in the language pairs you added it for.
• It applies to new translations. FluentC uses your entries when it translates text. Lines that are already translated stay as they are, so after you add or change an entry, search Translations for the old wording and edit any line that still has it.
• Keep entries short. A name, a term or a phrase works better than a whole paragraph.
• To leave something untouched, use the skip comment. For a block that must stay in its original language, see skip translation for specific content. To keep a single name the same in every language, add it to the glossary with the same text as source and target.

Translation memory also means reuse

FluentC saves every translation, so text that has been translated once is not translated again. That is why a repeated button label stays the same everywhere, and why a second visit is fast. The glossary sits on top of it: your terms first, then everything else reused or translated as usual. See how FluentC keeps translation costs down.

Related

• Translation memory, glossary and caching in FluentC for the overview.
• What to review first for the lines worth adding to the glossary.
• Keeping translations current for what to do when a term changes.