Feature Request: Mark machine translations as "Needs Review"
Background
ResXManager already supports TranslationState with the values:
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.
Feature Request: Mark machine translations as "Needs Review"
Background
ResXManager already supports
TranslationStatewith the values:NewNeedsReviewApprovedThis 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:
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
TranslationStateset toNeedsReviewinstead 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.