What and why?
HY-MT 2 supports model-specific controls that can shape how a translation is written. Let users choose the translation style they want so the same local model can better fit different notes, audiences, and use cases.
This should be a follow-up to #426, which integrates the HY-MT 2 models and their selection lifecycle.
Design considerations
- Confirm which upstream HY-MT 2 controls are useful and reliable before choosing the options we expose.
- Explore a clear, model-specific experience in translation settings and/or the translation flow.
- Decide whether choices are saved defaults, per-translation overrides, or both.
- Keep the feature hidden or unavailable for translation models that do not support these controls.
The exact controls and UX are intentionally open for product design and validation.
What and why?
HY-MT 2 supports model-specific controls that can shape how a translation is written. Let users choose the translation style they want so the same local model can better fit different notes, audiences, and use cases.
This should be a follow-up to #426, which integrates the HY-MT 2 models and their selection lifecycle.
Design considerations
The exact controls and UX are intentionally open for product design and validation.