2. Move the 'Suggest Machine Translation' checkbox and the warning message "Please check…" message above the two translation columns i.e. below the source and target select widgets. (They're not really related to the download/upload button area.)

In T206436#11878947, @Doc_James wrote:

We want it too keep machine translation on if the user goes to a new svg
but turn off if they change languages

J

Sent from Gmail Mobile

Great to hear. Thank you both for your support.
Do i need to close this task or will it be done automatically after next status 'patch for review' is completed?
I opened a new one with the changes suggested by Sam: https://phabricator.wikimedia.org/T425082
For the button vs checkbox, the original discussion was about having a 'sticky' behavior.
Indeed frequency of translation is low and just one additional click.

The code uses strpos($CSS, '#') and treats split selector segments as containing IDs.

I have added these two functionalities to the the merge request:
[done]

• color code translated field
• display warning messages to confirm to translations

Here is an example output in current state. Machine translation from EN to SP and EN to FR. As you can see, it requires manual correction from some fields, but 90%+ is accurate and returned with low latency (within 1 second)

In T206436#11741644, @Doc_James wrote:

99.9% of the time source language for out efforts will be English but it
would be good to be able to change it

J

Sent from Gmail Mobile

Working on the Source Language Widget:
the current setup implies a a logic issue: the source language is defaulted to the browser language.
For manual translation, it has no importance since the translator will identify both source and target language and translate accordingly.
however for machine translation, both need to be correct.

Linting errors cleared. now the test pipeline succeeded
i have changed the eslint config to allow for 'promise' to retrieve data from the api call asynchronously.
if another implementation is preferred let me know.

merge request (draft)
Priority:
implementing api call to cxserver to get translated field

Here is what it could look like with all comments taken into account:

1. checking the "Suggest machine translation": Yes, text field will be filled with machine translation. Will add a spinner / visible loading state when this happens.
2. difference between "Accept Suggestions" and "Submit": i want to make sure the acceptance of machine translation is intentional to ensure the quality. I can remove the "accept suggestions" button and add a warning text box instead.
3. I am not sure i understand the use case when a manual translation would already be in the box: is it if a user starts translating manually then ticks the 'suggest machine translation' ?

in any case, i propose to
3.a add the machine translation only when the text box is empty (no previous manual addition)
3.b change the background of machine translated box to light green to clearly indicate the boxes which are suggestions from the service
attaching a new mockup

I m trying to help with this task. here is a proposal
UI: mockup:

1. machine translation is optional with a tick box, must be actioned by user
2. if machine translation is selected, for each segments, propose a suggestion (API call)

3.user must intentionally accept translation before submitting