Skip to content

Submitting Translation Jobs

This guide covers how to submit content for translation using TMGMT Lara Translate.

Creating Translation Jobs

From Individual Content

  1. Navigate to Content (/admin/content)
  2. Find the content you want to translate
  3. Click Operations → Translate
  4. Select target language(s)
  5. Click Request translation

From Content Overview

  1. Go to Content → Translations (/admin/content/translations)
  2. Filter by content type, language, or status
  3. Select multiple items using checkboxes
  4. Choose "Request translation" from bulk operations dropdown
  5. Select target language(s) and confirm

From Translation Management Interface

  1. Go to Configuration → Translation Management → Jobs (/admin/config/regional/tmgmt_job)
  2. Click Add job
  3. Select Source language and Target language(s)
  4. Choose Source content (individual items, views, or custom selections)
  5. Click Save

Job Configuration Options

Selecting the Translator

  1. In the translation job form, choose Lara Translate from the provider dropdown
  2. Review job items that will be sent
  3. Configure any job-specific settings:
  4. Priority: Normal (default) or High
  5. Translation options: Override provider defaults if needed

Custom Translation Options

Per-job settings allow you to override provider defaults: - Style: Faithful/Fluid/Creative (different from provider setting) - Instructions: Job-specific translation guidance - Adapt to: Content type for this job only

Job Items and Processing

How Content is Chunked

The module automatically handles large content: - Content over API limits is split into chunks - Each chunk is translated separately - Chunks are reassembled while preserving HTML structure

What Gets Sent

For each piece of content, TMGMT sends: - Text content from all translatable fields - HTML formatting (preserves structure) - Content type context for better translations

What Stays Local

Non-translatable content remains unchanged: - File attachments - Image references - Entity metadata - Non-text fields

Monitoring Job Progress

Job Statuses

Your translation job progresses through these states:

  1. Submitted: Job queued for processing
  2. Active: Translation in progress via Symfony Messenger
  3. Needs Review: Translation completed, requires human review
  4. Completed: Translation imported successfully
  5. Rejected: Job failed (see error messages)

Item-Level Tracking

Each job contains multiple items: - Job items represent individual pieces of content - Items can have different statuses within the same job - Check individual item progress in the job detail view

Real-Time Updates

  • Job status updates automatically via Symfony Messenger
  • No need to manually refresh for status changes
  • Email notifications sent (if configured in TMGMT)

Continuous Translation

Automatic Submissions

When Continuous Translation is enabled: - Content automatically submits for translation when created/updated - Works with content revisions and workflows - Prevents manual submission steps

Configuring Continuous Translation

  1. Go to Configuration → Regional and language → Translation settings
  2. Enable "Enable continuous translation" for your content types
  3. Configure source/target language pairs
  4. Set default translator (choose Lara Translate)

Benefits

  • Non-blocking: Content saves don't wait for translation completion
  • Workflow integration: Fits into existing editorial workflows
  • Background processing: Translations happen asynchronously via Symfony Messenger

Translation Quality and Review

Quality Checks

Lara Translate provides built-in quality metrics: - Confidence scores: Translation accuracy indicators - Consistency checks: Terminology consistency within documents - Style compliance: Matches selected translation style

Review Process

  1. Automatic imports: Translations appear in the TMGMT interface
  2. Preview mode: Review before publishing (optional)
  3. Publishing: Make translations live when ready

Editing Translations

You can edit translations before publishing: - Fix minor issues without resubmitting - Preserve original formatting and metadata - Submit edits back to Lara for learning feedback

Best Practices

Content Preparation

  • Clean HTML: Remove unnecessary tags before submission
  • Consistent terminology: Use consistent terms in source content
  • Appropriate length: Break very long content into smaller pieces

Job Organization

  • Logical grouping: Group related content in single jobs
  • Language pairs: Process one target language at a time
  • Size management: Keep jobs manageable for processing

Quality Control

  • Test submissions: Start with small test jobs
  • Review samples: Check translation quality before large submissions
  • Feedback loop: Provide correction feedback to improve future translations

Troubleshooting

Common Job Issues

  • "No items selected": Ensure you've selected content items
  • "Unsupported language": Check language mappings in provider configuration
  • "Translation failed": Review error messages and retry if transient

Performance Considerations

  • Large jobs: May take longer to process due to message queueing
  • Network issues: Automatic retries handle temporary problems
  • API limits: Content chunking handles size restrictions