Thu, Feb 20
Wed, Feb 19
Message posted on Asamese Wikipedia to confirm the availability of the new system.
Tue, Feb 18
Mon, Feb 17
This seems to be an issue with the external machine translation services. I reported this to Google Translate team, feel free to add more details there or subscribe to the report to get further updates.
This involves dealing with wiki-specific templates, which seems to increase the complexity level of the tool for an aspect that translators should be responsible for (checking the quality of the source and the translation). Unless we observe this becomes a common problem, I'm more inclined to focus on other areas of improvement instead.
I think this got solved in the new version of Content Translation. The custom drop-down was replaced with a ooui dialog:
With the new version of Content Translation we improved the category support users can add any category they want to, which provides a path forward for cases where the initial mapping was not the best. Ideally, we could make the category mapping more advanced but I think there are other aspects more central to the translation process to be improved.
The Translation dashboard is expected to be refactored soon (T243583), which is expected to work well across the different skins.
Fri, Feb 14
Wed, Feb 12
Mon, Feb 10
Sat, Feb 8
Yes, that should fix the issue with fonts. Code merged on Tuesdays becomes deployed on Thursdays on group 2 wikis. Since this got merged last Wednesday it will be deployed next Thursday (Feb 13), if there are no issues with the deployment train.
Fri, Feb 7
Thanks for reporting, Zoranzoki21.
Recently we had s regression with styles that is being fixed in T243286.
In addition, the whole dashboard is in the process of being refactored (T243583), so these issues should be solved in the process.
The mockup was just a quick illustration while in a meeting, to present some ideas: (a) replace unit-related controls with a single entry point, (b) surface common/recent units early to facilitate selection, and (c) make the units visible next to the value when applied.
Thu, Feb 6
Wed, Feb 5
Tue, Feb 4
As captured in the summary document the exploration has been able to cover different aspects that are essential for our tools, illustrating them in a partial reimplementation of the dashboard. This follow-up ticket will focus on completing the refactoring: T243583: CX Dashboard: refactor and prepare for section translation