about attributes in the Parsoid output are messed up.

Looking at this fragment in https://www.mediawiki.org/api/rest_v1/page/html/Manual%3ACoding_conventions/4054714?redirect=false&stash=true:

There are two siblings with about="#mwt105" and data-mw. This doesn't look right to me; out of all siblings with the same about attribute, only the first sibling should have a data-mw attribute, that describes that content of all siblings. VisualEditor assumes that is the case, and "merges" all the siblings together, losing the data-mw on the second one.

T261181: Make Translate extension compatible with Parsoid is related

Also, wonder if this is another instance of what we saw in T260550#6393525

Thank you @Krinkle for getting this and T261181 documented! I think addressing these would be tremendously helpful for a lot of translation and documentation efforts by the Foundation, affiliates, and others on Meta-Wiki. I have heard from several folks that the lack of VE support for Translate makes them less likely to use it and nervous when editing pages that utilize Translate.

I think this work helps support both MTP (increasing documentation to ten languages) and Movement strategy goals - and appreciate the progress being made by the various teams involved! :)

Another example, without involving indentations or list items, perhaps helps to narrow down the relevant bug(s), unless it happens to be a separate cause:

• Text loss in parenthesis.
• Text became code/pre-formatted.

The preformatted text is because content of <translate>…</translate> tags is parsed in isolation, and the Translate extension forces them to start with a space.

We expect T261181: Make Translate extension compatible with Parsoid will take care of much of these issues. There, we are taking the approach of treating translate tag as a transparent annotation tag.