Topic on Talk:Content translation

Translating would be a nice thing for me to get help doing, as I could, and I may eventually do more of it, being a mid-active editor on enWP of Portuguese language. Two points that look quite incomplete so far:

- The interface is hard to understand. Starting from the initial page. It is clean and simple, yes, nice. But what does a "star" do? (save as favorite for future use? tag as in need to translate to suggest more to others? ...?) What does a cross do? (remove from suggestions? for now? for ever? remove from other people suggestions, by "downvoting" the article in some AI suggestion module? ...?) Yes, I'd bet on option one for both, and yes I can click and see - but I'd rather not go making a mess and it would be easier (for you and us) to add help and instructions as you code (a tool tip, or a side text, a link for a help page, something)

- The suggestions are of little use. That is not the fault of this project, I guess, the problem seams to be with wikidata. It does not allow to have link to article sections, so topics which have a "full" article in a language but "only" a section in the other show as suggestions.

Nevertheless it looks promising, I should try it out further soon(ish).

PS, Off-topic: It is the first time I use this talk page style. It does not look bad. Except that it has a set of thin moving stripes while saving a message. That is a very poor idea (unless the idea is to make me feel dizzy, in which case it works just perfect :-) Where do I tell about that?

Thanks for the feedback @Nabla.

Suggestions is one of the areas we are actively working on and currently there are many moving pieces. I agree that more guidance can be beneficial to clarify the user expectations on the features you mentioned. When testing the designs for joining translation campaigns we observed a similar need for clarifying first time experience. So we plan to work on this, and adding tooltips seems a good initial step. We also need to find the right balance to avoid distracting from the main user action in this context (i.e., pick a suggestion and start translating immediately).

Regarding the quality of suggestions. Recently we integrated an algorithm from the Research team that provides better suggestions based on your previous translations (more details). The Research team evaluated the quality of the approach and keeps working on improving the quality of the suggestions presented to users.

Regarding the discussion system, it is Flow. It has also a discussion page (using Flow itself) where issues about it can be discussed. In particular, the loading pattern you mentioned is inherited from Visual Editor, the rich text editor that Flow uses.

Thank you. Note that the problem that I am pointing with the suggestions will not improve at all by using previous edits / translations. The problem is that it suggests pages that do not need to be translated. A couple of exemples from my suggestions.

It suggests to translate (pt: to en:) , yet it is mostly covered at The problem is that Wikidata links (correctly) this en: page to . And that leaves "pt:Sexo vaginal" as if it had no counterpart in en: although it has. And then, we can not create one on wikidata because linking to the obvious choice of is forbiden (?) by wikidata because it is a redirect to "en:Sexual intercourse", apparently because it already has a pt: counterpart. It may work out fine, but it may be a aquite frustrating experience, someone taking the effort to translate a page, only to get it deleted (or merge / redirected) as mostly a duplicate hours later...

Similar problem with and

Thanks for pointing about Flow (I've read about it, but I couldn't remember what to look for - will post there)