When translating from Hindi to Urdu, MT is disabled by default (no-mt). The message in the MT card in the sidebar is "cx-tools-mt-not-available". The correct message to show there is "cx-tools-mt-dont-use".
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| MT Card: Correct the menu when MT is disabled by default | mediawiki/extensions/ContentTranslation | master | +12 -15 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T76456 Language Engineering tracker of trackers (tracking) | |||
| Open | None | T127695 Design polishing for Content Translation | |||
| Resolved | santhosh | T128059 Better announce new optional MT services available | |||
| Resolved | santhosh | T117035 When MT is disabled by default in ContentTranslation, cx-tools-mt-not-available is shown instead of cx-tools-mt-dont-use |
Event Timeline
Comment Actions
Just guessing: maybe cxserver configuration should have "disable-mt" instead of "no-mt" for such languages?
Comment Actions
This should be resolved before enabling adding MT support to more languages without making it default.
Comment Actions
The current UI:
Can you mention the exact English string you want to change instead of message keys?
Comment Actions
The current UI:
Can you mention the exact English string you want to change instead of message keys?
It doesn't appear in this screenshot. It appears to be fixed for this language pair. Maybe now it's just a matter of correct configuration. If it's indeed so, then this bug can be closed.
Comment Actions
No, there is indeed an issue. I configured a language pair as non default. See the UI
I set Apertium as non-default MT for en-es. What I would expect is 3 items in menu, instead of 4
- Use source text
- From Apertium
- Start from scratch (wording can be different)
And if Apertium is default, In different order:
- From Apertium
- Use source text
- Start from scratch (wording can be different)
@Pginer-WMF comment please.
Comment Actions
@Pginer-WMF comment please.
Some thoughts about the labelling and options:
- We should have 3 options instead of 4 in the above examples.
- "Not available for X" does not make sense as an option to chose.
- "Not available for X" only makes sense as a label in the card when there is no other MT available (as default or non-default).
- The proposed title of the card was "Automatic translation" to cover beyond MT including strategies such as "copy source".
- We don't need to reorder the options. Keeping the fallback options (use source and use an empty paragraph) at the end makes sense.
- For MT services we may want to label them as "Use X" instead of "From X" especially since we made the changes to take effect immediately.
Given the above considerations, here is a proposed approach for each case (using Apertium and Spanish as examples):
MT not available
- Card title: "Automatic translation"
- Initial value: "Not available for español"
- Options:
- "Use source text"
- "Don't use automatic translation"
In this case, the initial value is a default empty state that behaves like "use source text" but helps to highlight that there are no MT options beyond the fallbacks.
MT available only as non-default
- Card title: "Automatic translation"
- Initial value: "Use source text"
- Options:
- "Use Apertium"
- "Use source text" (✓)
- "Don't use automatic translation"
MT available as default
- Card title: "Automatic translation"
- Initial value: "Use Apertium"
- Options:
- "Use Apertium" (✓)
- "Use source text"
- "Don't use automatic translation"
Comment Actions
Change 274668 had a related patch set uploaded (by Santhosh):
MT Card: Correct the menu when MT is disabled by default
Comment Actions
Thanks @santhosh!
This looks good.
The only piece missing is to adjust the label for MT options: "Use Apertium" instead of "From Apertium".
It is a small detail to (a) keep the language consistent with other options, and (b) helps to convey that once you selected it it will be applied immediately (which is a behaviour we changed recently).
If this is not trivial, we can create a separate (probably low-priority) ticket.
Comment Actions
The only piece missing is to adjust the label for MT options: "Use Apertium" instead of "From Apertium".
Comment Actions
Change 274668 merged by jenkins-bot:
MT Card: Correct the menu when MT is disabled by default
Comment Actions
I like the general solution, but I'm still confused about the change of "Machine translation" to "Automatic translation". Pau's explanation is:
The proposed title of the card was "Automatic translation" to cover beyond MT including strategies such as "copy source".
This wording doesn't convey this meaning. "Copy source" is not translation, so it cannot be included under "Automatic translation". We stay with the same problem that we had with "Machine translation".
I would consider changing the title entirely, to something like "Filling the paragraph", but better suggestions are welcome. (Should I open another task?)
Comment Actions
This wording doesn't convey this meaning. "Copy source" is not translation, so it cannot be included under "Automatic translation". We stay with the same problem that we had with "Machine translation".
I don't think it is currently "a problem". What I proposed was to make it a little bit more generic. There is content that is crafted by the user and there is content that gets added to the translation automatically. When content is added, users may wonder why and how to control it (i.e., checking alternatives). "Automatic translation" seems to describe the process of content being added in the user behalf, in the translation, automatically.
Making it too generic makes the connection less obvious. For example, "Filing the paragraph" makes it unclear which is the purpose of such filling.