Thanks for asking for my opinion :)

The feature in general, and the text in the current messages and on https://www.mediawiki.org/wiki/Growth/Revise_Tone#Designs look OK to me. I can't see any major red flags.

The example Wikipedia-like texts will have to be translatable, of course.

"Weasel word" is a jargon term known in the English Wikipedia. Corresponding terms already exist in the help pages of at least some other languages. It will have to be clearly explained in qqq, with links and examples. But it's not really a problem. (It's also used in the PageTriage extension, which is only enabled on the English Wikipedia AFAIK. For what it's worth, it's translated into some languages already.)

Perhaps the most significant comment I have at this point is the word "DRAFT" in the beginning of several recently-added messages. It's not really needed there. If it's important for developers, product managers, or designers to say that a message is not final and may change, we usually don't put this in the messages themselves, but in qqq. A good way to do this is to put {{experimental}} in the beginning of the qqq string, and it will be shown to the translators in a standardized way. I've already done this on translatewiki for the messages with "DRAFT", and it will be updated in Gerrit some time soon. I recommend removing the word "DRAFT" from all these messages. (And when the messages are final and no longer experimental, please try to remember to remove {{experimental}} from qqq.)

In T407580#11341310, @Amire80 wrote:

Thanks for asking for my opinion :)

The feature in general, and the text in the current messages and on https://www.mediawiki.org/wiki/Growth/Revise_Tone#Designs look OK to me. I can't see any major red flags.

The example Wikipedia-like texts will have to be translatable, of course.

"Weasel word" is a jargon term known in the English Wikipedia. Corresponding terms already exist in the help pages of at least some other languages. It will have to be clearly explained in qqq, with links and examples. But it's not really a problem. (It's also used in the PageTriage extension, which is only enabled on the English Wikipedia AFAIK. For what it's worth, it's translated into some languages already.)

Perhaps the most significant comment I have at this point is the word "DRAFT" in the beginning of several recently-added messages. It's not really needed there. If it's important for developers, product managers, or designers to say that a message is not final and may change, we usually don't put this in the messages themselves, but in qqq. A good way to do this is to put {{experimental}} in the beginning of the qqq string, and it will be shown to the translators in a standardized way. I've already done this on translatewiki for the messages with "DRAFT", and it will be updated in Gerrit some time soon. I recommend removing the word "DRAFT" from all these messages. (And when the messages are final and no longer experimental, please try to remember to remove {{experimental}} from qqq.)

Thank you! Useful to know about {{experimental}}! Are these templates documented somewhere? I glanced at https://www.mediawiki.org/wiki/Help:System_message#Message_documentation but did not find guidance about that, but maybe I missed it.

In T407580#11341770, @Michael wrote:

Thank you! Useful to know about {{experimental}}! Are these templates documented somewhere? I glanced at https://www.mediawiki.org/wiki/Help:System_message#Message_documentation but did not find guidance about that, but maybe I missed it.

Good point. I've added {{experimental}} and a few other useful templates to that section.

Change #1202162 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat(Revise Tone): finish i18n work of onboarding quiz

https://gerrit.wikimedia.org/r/1202162

Test wiki created on Patch demo by MGrosse-WMF using patch(es) linked to this task:
https://93c9feef05.catalyst.wmcloud.org/w/

For question 3, I think we are missing a space after the period:
This term adds the writer’s opinion rather than describing events objectively.Learn more

Test wiki created on Patch demo by MGrosse-WMF using patch(es) linked to this task:
https://4f160eae2a.catalyst.wmcloud.org/w/

Test wiki on Patch demo by MGrosse-WMF using patch(es) linked to this task was deleted:

https://93c9feef05.catalyst.wmcloud.org/w/

In T407580#11347197, @KStoller-WMF wrote:

For question 3, I think we are missing a space after the period:
This term adds the writer’s opinion rather than describing events objectively.Learn more

Fixed!

In T407580#11341802, @Amire80 wrote:

In T407580#11341770, @Michael wrote:

Thank you! Useful to know about {{experimental}}! Are these templates documented somewhere? I glanced at https://www.mediawiki.org/wiki/Help:System_message#Message_documentation but did not find guidance about that, but maybe I missed it.

Good point. I've added {{experimental}} and a few other useful templates to that section.

Thanks!

Change #1202162 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat(ReviseTone): finish i18n work of onboarding quiz

https://gerrit.wikimedia.org/r/1202162

The Revise Tone onboarding as a whole can now be meaningfully tested on beta-enwiki.

If the onboarding is being closed with the "don't show again" checkbox checked, then that will cause the onboarding to not show again. That can be reverted by running the following in the browser console: (new mw.Api).saveOption( 'growthexperiments-revisetone-onboarding', '0' );.

I spotted a couple of issues with number format while testing the dialog in enwiki forcing the language to arabic using uselang=ar:

I think the step counter should needs to be fixed, right @Amire80 ? About an example sentence having a number that we need to format for proper translation I think we're adding some unnecessary complexity but we could handle it by passing 1847 as a fixed param. meh, if it the whole message is translatable there's no issue with the 1847 😅 .

In T407580#11358211, @Sgs wrote:

I spotted a couple of issues with number format while testing the dialog in enwiki forcing the language to arabic using uselang=ar:

I think the step counter should needs to be fixed, right @Amire80 ? About an example sentence having a number that we need to format for proper translation I think we're adding some unnecessary complexity but we could handle it by passing 1847 as a fixed param. meh, if it the whole message is translatable there's no issue with the 1847 😅 .

@Dyolf77_WMF Does the screenshot Sergio added look problematic? Any thoughts on if we need to improve the localization of these strings?

In T407580#11392783, @KStoller-WMF wrote:

@Dyolf77_WMF Does the screenshot Sergio added look problematic? Any thoughts on if we need to improve the localization of these strings?

@KStoller-WMF No problem with the numbers if they will be displayed on ar.wp where the configuration of the wiki displays 'Arabic' numerals: 1, 2, 3, etc.

Outside ar.wp, all other projects, by default, they are using the Eastern Arabic numerals. Given that I translated the text of 3 of 5 and 1847 using Arabic numerals, I don't see any issue.