Skip to content

Mark machine translations as "Needs Review" #762

Description

@tc-thats-me

Feature Request: Mark machine translations as "Needs Review"

Background

ResXManager already supports TranslationState with the values:

  • New
  • NeedsReview
  • Approved

This state is already persisted and used throughout the application (including XLIFF import/export).

Currently, machine translations can optionally be prefixed (for example #TODO#_) potentially to indicate that they require human review.

Problem

Using a text prefix makes it difficult to generate a clean review package for translators because the workflow becomes:

  • Machine translate
  • Export
  • Remove the prefix
  • Filter only prefixed entries
  • Remove already-reviewed entries

This mixes workflow state with the actual translation text.

Proposal

Add an optional configuration setting:

Mark machine translations as "Needs Review"

When enabled, machine-translated entries would have their TranslationState set to NeedsReview instead of relying solely on a text prefix.

This would allow users to filter/export entries requiring review using the existing translation state infrastructure while remaining fully backward compatible with the current prefix-based workflow.

I'd be happy to implement this if the approach aligns with the project's direction.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions