Content memory

The content memory holds pairs of source and target text segments that Bowrain reuses across projects to keep translations consistent and avoid re-translating what the workspace has already settled. In the engine the store is the translation memory (TM); this page uses TM for the mechanism — entries, matches, and scores.

The content memory and terminology live on the server, shared across every project and translator — searchable and versioned.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Opening the content memory

There are two ways to open the content memory browser:

1. From a project — click the Content memory button in the project view header. This opens the browser with the project's source and target locales pre-selected.
2. From the sidebar — click Content memory in the main sidebar to browse the workspace-scoped content memory without locale pre-filtering.

Browsing Entries

The browser displays entries in a paginated table with these columns:

Column	Description
Source	The source language text
Target	The target language translation
Source Locale	Language code of the source text
Target Locale	Language code of the target text
Updated	Date the entry was last modified
Actions	Edit and Delete buttons

The entry count badge in the header shows the total number of entries matching current filters.

Searching

Type in the search box to filter entries by source or target text. The search uses debounced input (300ms delay) to avoid excessive API calls while you type. Results update automatically as you type.

Filtering by Locale

Use the locale filter dropdowns to narrow entries:

• Source locale filter — show only entries with a specific source language
• Target locale filter — show only entries with a specific target language

Filters can be combined with text search. Changing a filter resets to page 1.

Adding Entries

1. Click Add Entry in the header
2. Fill in the form:
   • Source text — the original language text
   • Target text — the translation
   • Source locale — select from available project locales
   • Target locale — select from available project locales
3. Click Add to save, or Cancel to discard

Editing Entries

1. Click Edit on an entry row
2. The target text becomes an inline text input
3. Modify the translation
4. Click Save to confirm, or Cancel to discard changes

Only the target text can be edited inline. To change the source text or locales, delete the entry and create a new one.

Deleting Entries

Click Delete on an entry row. The entry is removed immediately and the table refreshes.

Pagination

When there are more than 50 entries, pagination controls appear below the table:

• Previous / Next buttons to navigate pages
• Page X of Y indicator showing current position

Content memory in editing and review

The content memory also assists translation work outside the browser:

• Context panel — the translation editor shows per-block TM matches with scores and match types, with one-click apply.
• Bulk recycle — Pre-process pre-fills targets from the content memory across the whole file; exact and high-confidence fuzzy matches land as drafts you can review.
• Apply exact Memory — Review fills selected blocks from exact (100%) matches.

Match scores

Each TM match receives a score from 0 to 100% representing how closely the source text matches the stored entry. Matches are color-coded:

• Green (100%) — exact match
• Yellow (70–99%) — fuzzy match
• Lower scores appear with reduced emphasis

Bowrain's matching accounts for inline formatting differences, so a source segment and a stored entry can match even if their tag structure differs slightly. For more on how the underlying engine matches across projects, see the framework's content memory reference.