Fri, Jun 15
Thu, Jun 14
As described above (T190203#4278479) this seems not to be solved for some cases. We need to investigate which are those and iterate the solution.
The issue has been confirmed for version 2, so I created a follow-up ticket to get it fixed: T197221: CX2: Link translated articles with other languages through Wikidata automatically
My preference is for 1. I think it has the advantage of presenting the label UI elements as single unit. It also keeps the label part less prominent than the main piece of information (the link target) which should be proportional to the expected use.
The drawback of having less room for the label does not seem a big problem. The purpose of showing (part) of the label is just to give a reference about what the element refers to. The real label is fully shown as part of the document itself anyway.
Wed, Jun 13
This comment seems to suggest a regression. When translating w:en:Die Streuner -> w:ru:Die Streuner the category "Articles with hCards" was added to the translation.
We may want to verify and consider creating a follow-up ticket to fix the issue.
This issue was also reported by a translator here.
Tue, Jun 12
Pointer cursor makes sense for both the tags and the menu icon.
This issue happened also when translating 1936 Cansiglio earthquake from English to Italian in production. Note that in this case there is no MT service available, so the failure happens when the source version of the (5th) paragraph is added.
As per @Nikerabbit comment, we can consider to use a category instead of an edit tag. The ticket goal is to provide a tool for editors to find easily the content that is more likely to be problematic, and I'm ok with using whichever mechanism works best for that. Categories can be removed, which works better for marking issues on content that can be resolved. Although categories cannot be filtered in Recent Changes, there are plans to support it in the near future.
Mon, Jun 11
Fri, Jun 8
Thanks for the feedback, @jmatazzoni . I made some more explorations. Each has some pros and cons but all should make the expand-collapse relation more clear while keeping the positions consistent and avoid making the hide action too prominent:
> What is the right thing to do in ULS: to set it globally or to set it locally? I can imagine users that may want both things, and I cannot think of a default that is right for everyone.
Currently there is some very basic support for campaigns in Content Translation. It is not very visible because campaigns need to be created by hand based on a category. We identified this as an aspect to improve for campaigns with a large number of articles. So i think the ticket is still relevant, even if the designs need to be updated to catch up with more of the recent changes.