From the video it seems that in addition to the console error, the translate content is not added to the document and the source content is added instead because of the failure. We may need to investigate if this is produced because of the tool is having problems with a particular kind of content or it is a more general issue.
Mon, Jun 24
This seems relevant to identify how well the tool supports different types of content (T191389) and references (T200786). We could better identify the most problematic elements and capture the progress (i.e., the improvements in support should reflect on the decrease of issues).
Yes, mapping templates based on parameter names and aliases is a limited approach based on the information about templates that exists today. As mentioned in T225989#5273626, we plan to provide cleaner and more scalable mechanisms.
Content translation integrates external translation services. These provide translations that are not always accurate and users are expected to modify them. The tool exposes user corrections for those in charge of the services to improve them, but content translation just integrates the translations those provide without providing special support for particular words on specific language pairs. There is a related ticket to prevent repeated corrections as a more general solution (T96165).
The new version of Content translation now uses the same editing surface as Visual Editor, so it should support the formatting described. If there are still issues feel free to repoen and provide details on how to reproduce them. thanks!
This is covered already in T168287: CX2: Warning about article having changed too much, the pending parts about the restoring process will be covered in T220790: Restore using updated content only when no user data is lost, using the original version as a fallback.
Fri, Jun 21
Templates are created independently in each wiki. In order for Content translation to know how to copy the parameters from one in the source article to the equivalent one in the target wiki, metadata is needed. Currently Content translation relies on templateData to know which parameters to copy the information of the template over. The "url" parameter works because it has the same name in both languages. For "tytuł", Polish Wikipedia editors can edit the templateData to add a "title" alias that help the tool to know they are equivalent.
As an icon the closed version helps to see it as a single shape. Chemical diagrams may have their norms, but I'm not convinced that we should replicate those when creating icons. Similarly, cartography has its norms like indicating the scale of a map, but that does not apply when creating an icon representing a map.
Thu, Jun 20
Wed, Jun 19
My understanding is that for this ticket, the missing parts are:
- If the user adds information to the reference (or the template it contains), it will be rendered normal (blue) and the warning will disappear.
- When publishing the translation, the missing references will be skipped if they are still empty or contain only an empty template. That is, for cases where the reference is still marked as missing (grey) and the user has not edited it.
Tue, Jun 18
The issue was reported in this comment.
Mon, Jun 17
Based on initial testing, the templates used to show a country link next to its flag such as IND for India were adapted to the corresponding template in French (Inde). From the translation editor, the adaptation looks good, but the result after publishing shows that the generated contents get preceded by an unexpected "lien=|bordure" markup:
Fri, Jun 14
The current limits seem to be too strict based on recent feedback (1) (2), (3), (4), (5) (6). We may need to adjust the limits for the regular user to make them less strict. In this way, most users will have room to accommodate the cases where MT works well, while we make the bar higher after one of their translations gets deleted in the last month.
Reopened as per T224437#5258003