The language search seems to be working more flexibly now. I tried the example from the original report and a few more, and they work as expected:

Some initial notes and reflections:

With the unified dashboard using a different technology, this issue is no longer happening:

In T322740#10805317, @Jdlrobson-WMF wrote:

@Pginer-WMF what is the latest status of this epic? I am going to be taking some extended time off and I want to know if I need to make arrangements for while I am away.

In T356194#10803907, @PWaigi-WMF wrote:

@Pginer-WMF Could you check this one? I'm unable to reproduce it.

The number of languages shows correctly on the Confirm step. Notice however that this creates an inconsistency with the information shown at the Search step. Below, you can see the two steps: searching for the article title shows the first result with "2 languages" indicator, and taping on it opens the Confirm step with "3 languages" indicator:

In T392753#10803052, @eamedina wrote:

A couple of other questions:

One aspect worth detailing/illustrating is how collapsible items work in search. For example, how a query such as "Africa" could let users find both the African continent and the South Africa country.

@SGautam_WMF The proposal looks good. One aspect we may want to detail a bit more is how naming defines sub-collections. We may want to clarify whether the parent collection needs to be defined explicitly or not for sub-collections to exist. Some examples below of how the naming conventions could work:

In T392753#10779618, @SGautam_WMF wrote:

1. Adjustments in the search placeholder. The search placeholder in the designs reads as "Search for a topic..." regardless of the tab selected. I think it may be helpful for the placeholder to reinforce the current selection. For example, if the user selected the "Collections" tab, the placeholder could read as "Search for a collection".

I have added a section below the main search area section in the task description.

@SGautam_WMF The proposal looks good. Some aspects we may want to consider for the specification:

I have been trying the demo tool with some examples comparing it with Content Translation and a diff tool as reference. Overall, I have the impression that the new algorithm works better than the current one. It is more sensitive to changes, thus it would account for more of the user modifications and avoid cases where the user has modified the translation and the tool prevents them from publishing. In any case, we may want to keep an eye on deletion rates if the change is applied.

In T327063#10764979, @SBisson wrote:

@Pginer-WMF

That is, the "New page" option will link to Wikipedia:Requested articles when the page is available, and not show the action when it is not.

With this condition, there is a small but real risk that the Special:Contribute page has no contribution options at all. Do we want to risk it or do we prefer to always show the New page option even if it has it's suboptimal default target (Special:Wantedpages)?

@SGautam_WMF, before development starts, we may want to include a link on the collection view to the page where the page was tagged as a collection. For example, the Wiki99 sustainability collection view would link to https://meta.wikimedia.org/wiki/Wiki99/sustainability

Regarding the communication of saving issues, there is a related ticket from a decade ago: T106690: CX2: Communicate that auto-save is retrying automatically after an error
My understanding is that saving is automatically re-tried after some time. If that is the case, it would be good to communicate that too.

I added a proposal in the "Proposed approach" section from the description. It is intended to provide the alternative option to re-translate the whole article where it is relevant (i.e., not showing when coming from suggestions), and make it more clear and less prominent. This is expected to still allow some of the workflows based on overwriting previous publications, while reducing confusions and the risk of accidental overwrites. Feel free to share your thoughts.

In T260115#10751721, @SBisson wrote:

@Pginer-WMF here's some screenshots from the patch above:

mobile	tablet	desktop

In T387108#10748333, @eamedina wrote:

@SGautam_WMF @Pginer-WMF —Patch has been approved but a question came up regarding the copy. What do you think would be the best copy for the different cases below?

• if there are multiple sections: "X minutes to translate N sections"
• if there's only 1 section (not-preselected): "X minutes to translate 1 section"
• if there's 1 preselected section: "X minutes to translate this section" or "X minutes to translate {section-title} section"

In T352391#10748086, @hueitan wrote:

• This is a cute cat -> This is a very cute cat
  • only the "very" was added, so is this
    • 3/6 modified (because "very cute cat" are not in order); or
    • 1/6 modified (consider "cute cat" still in same order)?

The general functionality seems in place. Some details on labelling captured below:

In T259470#10738693, @SBisson wrote:

@Pginer-WMF FYI

Confirmation step, notice that the language selector is full width

Select sentence step, with the language selector full width (work in progress patch)

In T259470#10728378, @SBisson wrote:

@Pginer-WMF the mockup in the task description seems a bit old. The style of the language selector gives it away. Do you want to update it before I get to far on this task?

For the reference breakpoints the adaptation of the language selector works as expected for the narrow and wide cases.

Confirmed. It works as expected.

Great! The issue described in T386118#10604901 is no longer happening.

The "New translation" button is not showing where it was not supposed to. So moving to product sign-off.
However, I noticed a glitch in this same area, captured in T391468 in case it is relevant.

With the new dashboard, this functionality is already available.

With the new dashboard, these issues should no longer happening. Feel free to reopen if that is not the case.

With the new dashboard, these issues should no longer happening. Feel free to reopen if that is not the case.

With the new dashboard, these issues should no longer happening. Feel free to reopen if that is not the case.

With the new dashboard, these issues should no longer happening. Feel free to reopen if that is not the case.

I wanted to share a couple of proposed aspects to measure that have been surfaced in several conversations in the past as the impact of translations have been analyzed:

In T329570#10715706, @Iniquity wrote:

@Pginer-WMF hi! For context, why it works only in main namespace?

https://ru.wikipedia.org/wiki/Википедия:Искусственный_интеллект

The specific issue with redirects is solved. The links in the description now lead to the intended destinations.

In T351734#10610886, @ngkountas wrote:

@Pginer-WMF regarding the part B) of the task and specifically for the overlay, instead of the proposed backdrop color (Base20 #54595D, 85% opacity or rgba(84, 89, 93, 0.85)), can we use codex @background-color-backdrop-dark (rgba( 0, 0, 0, 0.65 )) design token for better consistency?

• Now the mobile experience is supported on Wikipedia for all languages.
• A comment from a user asking for access to translation from the app suggests that they are using the notifications as a workaround to access the tool.

In T364129#10608548, @abi_ wrote:

I've updated the code to display the dialog from two entry points:

1. "Review the automatic translation" card
2. "Correct the translation" in translation viewer options

@Pginer-WMF Do we want to instrument this entry-point too by adding a campaign parameter?

In T376860#10672494, @abi_ wrote:

One problem is that the reference section does not load especially if we are translating a long article. Eg: https://language-cx.wmcloud.org/index.php/Special:AutomaticTranslation?page=Tokyo&from=en&to=hi&step=translation, try expanding the संदर्भ section