Context resources

Understand how the style guide, scenario, phrasebook, and project knowledge complement one another during translation.

What context resources do

Context resources turn project decisions and analyzed source structure into reusable guidance. They do not replace the source or target text; they help translators and translation tools make consistent decisions while working in the Editor.

  • Style guide: project-wide or target-language-specific writing rules.
  • Scenario: source structure, events, entities, and relationships discovered from selected files.
  • Phrasebook: reusable sentence patterns and their variable slots.
  • TM and TB: previously translated segments and approved terminology, managed as separate reference resources.

Choose the right resource

Record an explicit editorial rule in the style guide, an approved word in the termbase, and a reusable full-sentence structure in the phrasebook. Use Scenario when the guidance depends on where a line appears, who is involved, or how events and entities relate.

Recommended workflow

  1. Upload and commit the source files that define the current project content.
  2. Add stable writing rules to the style guide and review the project and language tabs.
  3. Arrange source structure in Scenario, save it, and analyze only the files and categories you intend to process.
  4. Run phrasebook analysis where repeated structures matter, then review splits and master bindings before relying on them.
  5. Open the Editor and check the active language, file, status, and reference suggestions before committing translations.

Access, freshness, and limitations

The project menu and available actions follow your current project access. A read-only page lets you inspect context but disables changes and analysis. Missing menu items usually mean that the current project or your access does not expose that resource.

Check context before translation

Style guide
Check project-wide rules and the tab for the target language.
Scenario
Check which source files belong to Main Story, Events, Unclassified, or Excluded.
Phrasebook
Review repeated sentences, their split, and the master pattern selected for each segment.
  1. In the project sidebar, open Context and review the resource cards available for the project.
  2. Open Style guide and confirm the enabled rules for the target language.
  3. Open Scenario and Phrasebook; wait for active analysis to finish and review the saved results.
  4. Open the assigned file in the Editor and confirm the target language and visible reference suggestions.

After completion: You begin translation with the current saved rules, source arrangement, and reviewed phrase patterns visible in their respective screens.

Problem

A context menu or action is missing.

What to do

Confirm that you opened the intended project. If the page is read-only or the action stays hidden, ask a project manager to check your project role.

Problem

Editor suggestions do not match a recent context change.

What to do

Return to the owning screen, confirm that Save or the analysis completed successfully, then reopen the file or refresh the Editor.

Scenario checklist from Context

Main Story
The primary ordered flow. Drag source items here in the order translators should understand them.
Events
Named groups for side stories or related files. Add, rename, filter, or delete an event from its header.
Unclassified / Excluded
Unclassified items still need placement. Excluded items stay outside Scenario analysis until moved back.
Reset / Save
Reset reloads the last saved arrangement. Save records the current arrangement; unsaved dragging is not retained.
  1. In the project sidebar, under Context, select Scenario and stay in the Scenario view.
  2. Drag Unclassified items into Main Story or an Event; move items that should not be analyzed to Excluded.
  3. Select Save and wait for the success message, then select Analyze.
  4. Review the confirmation scope, start the run, and follow its visible task status until completion.
  5. Open Entities and Mind Map, choose All or a narrower scope, and review names and relationship direction.

After completion: The saved arrangement remains after reload, and completed analysis results are available in Entities and Mind Map for the selected scope.

Problem

Save or Analyze is disabled.

What to do

Save requires an unsaved arrangement change. Analyze is unavailable in read-only mode or while another analysis is being prepared or run. Check the visible task first.

Problem

Dragged items returned to their old positions.

What to do

The arrangement was not saved or Reset was selected. Arrange the items again and select Save before changing view or leaving.

Problem

Analysis finished but no new entity appears.

What to do

Confirm that the intended files were not Excluded and that the Entities scope includes them. A completed analysis can legitimately find no new entities.

Carry context into the Editor

Contents
Filters the table to one or more content groups. Search, Select all, and Clear all change only the current view.
Target status
Shows whether a row is still a draft, committed for the next workflow step, approved, locked, or needs attention after a source change.
Reference and detail panels
Shows suggestions, issues, comments, metadata, spellcheck, or history for the focused row. A suggestion changes text only when you apply it.
Deliver
Opens the delivery flow when the file and your role allow it. It is separate from committing an individual row.
  1. Open an assigned source file and confirm the file name, target language, and Contents selection in the header.
  2. Focus an editable target cell, enter the translation, and apply any reference suggestion you intend to use.
  3. Commit or confirm the row with the available row action, then read the updated target status.
  4. Open History for the row if you need to verify the saved change; continue to the next visible row.

After completion: The target text and status remain after leaving and returning to the row, and the saved change appears in History when history is available.

Problem

A target cell is read-only.

What to do

Check the row status and collaboration indicator. Approved or locked rows, rows outside your assignment, and rows focused by another collaborator may not be editable. Ask the project manager if the assignment or stage must change.

Problem

An edit conflicts after reconnecting.

What to do

Open the conflict shown for that row and language, compare the local and current versions, and choose the version to keep. Do not repeat the edit blindly.

Problem

The saved text is present but status did not advance.

What to do

A draft save and an explicit commit are different actions. Focus the row, use its commit or confirm action, and verify the status changes. If the source changed, review and commit the new target again.