Local messages have been created by @putnik (I didn't know about them).

I completely agree, it would probably be desirable to display user groups that can edit the page.

Hi! What's the progress and status? :)

In T2156#11396289, @Nardog wrote:

If you're proposing /* top */ appear translated rather than "→top" only in the parsed result (and still linking to #top), I can see some reason for it. But if you mean changing /* top */ and adding an ID to the top of every page, that's not something you should entertain so willy-nilly.

What I'm saying is that the edit summary shouldn't contain English words that part of the user don't understand.

/* top */ must be translated of course. There shouldn't be any non-localized strings in the interface :)

Linked this topic in Community Wishlist wish: https://meta.wikimedia.org/wiki/Community_Wishlist/W345 :)

In T333716#11287200, @Novem_Linguae wrote:

so we can probably close this ticket soon.

We won't be able to close this ticket until the map has the summarized and cleaned data.

Hi! What's the plan for implementing the new data? I just noticed that views are hidden too: https://stats.wikimedia.org/#/ru.wikipedia.org/reading/page-views-by-country/normal|map|last-month|(access)~desktop*mobile-app*mobile-web|monthly.

In T355164#11226304, @DLynch wrote:

Sorry, I specifically meant the client-side part of DT — my understanding is that currently it’ll correctly place the new topic wherever it’s configured to, but the DT editor will appear at the bottom of the page always instead of where the insertion will happen.

I can't edit templates at all: https://ru.wikipedia.org/wiki/Special:CommunityConfiguration/TemplateData-FeaturedTemplates

It seems to me that some Cloudflare server is blocked or has down. Everything works on another provider. Thanks for the tip on solving the problem :)

Yes, it is Cloudflare issue, I think.

Hm, I tried to open from PC and mobile, the same issue.

In T404502#11193530, @Nikerabbit wrote:

I got an email that says:

✖ A remote mirror update has failed.

Not sure if the translation update itself was successful?

In T355164#11083196, @DLynch wrote:

My recollection was that in particular there was debate about whether it should be implemented as new magic words, or as parser functions. @cscott may want to speak more on that.

We also felt it'd need to work with the DiscussionTools new-topic tool. Then, given that and the relative tininess of it, it might make sense to just fold it into DiscussionTools via a patch, rather than needing to maintain inter-extension dependencies on that kind of placement code.

Thanks! :)

In T404502#11183778, @abi_ wrote:

@Iniquity, Please give access to https://gitlab.wikimedia.org/l10n-bot to push the changes to the repository.

Done :)

Also message documentation (qqq.json) is missing. Will you add it after the project is onboarded on translatewiki.net?

Done :)

In T396709#11185798, @DLynch wrote:

The drawback to applying it post-load with a JS API you provided, as was requested for Convenient Discussions, would be that this changes the layout of the page -- a sudden flash of all the text on a talk page reflowing because every single signature now takes up 20px more horizontal space is going to cause some problems with things like following header/comment permalinks.

I can be corrected by @Jack_who_built_the_house, but for CD is ok :) СD is currently redrawing part of the interface to display normal signatures.

In T399096#11180806, @Dreamy_Jazz wrote:

In T399096#11179093, @Iniquity wrote:

Im sorry, but reopen. Still wrong count :(

Could you provide a recent example of this?

I do see that for DWalden has a count of 21 in the UserInfoCard but seems to have created 22 articles, but not sure if you have other examples to help us narrow this problem down

<s>Can we use https://prettier.io/ (https://github.com/prettier/eslint-config-prettier) instead of deprecated eslint formatting rules? :)</s>
https://eslint.org/blog/2023/10/deprecating-formatting-rules/

Im sorry, but reopen. Still wrong count :(

Thanks! It works :)

In T404471#11177470, @JJMC89 wrote:

I cannot reproduce. The tool's home page successfully loads and so does the example linked there.

In T404471#11177459, @JJMC89 wrote:

Toolforge is not part of prod.

Yes! It works, thanks :)

In T403419#11151881, @Sophivorus wrote:

I recently changed max-width: 700px; for width: 700px; in the CSS of #proveit-body. Is the issue still happening to you? If yes, what browser are you using? Thanks!

I don't know who implemented it :) But done.

It may be necessary to change the priority of this task due to T396789.

Thank you! The best! :)

In T358450#11134242, @Sophivorus wrote:

However, I agree it's confusing to have them show when clicking the "Add reference" button, so I just added a line of code that excludes those specific templates from the "Add reference" form.

Thanks for the fix! :) I think it would be more intuitive if they were shown in reference, because they can't be "not reference". But with a specific parameter in the settings. Something like that:

'proveit-templates': [ // Citation templates (without namespace)
	'Cite web',
	'Cite Q',
	'R',
	'sfn': {
		'type': 'noref'	
	},
	'Sfnm'
],

or

'proveit-templates-noref': [ // Citation templates (without refs)
	'Cite Q',
	'R',
	'sfn',
	'Sfnm'
],

Hi! Thank you!

Sorry, I'll reopen it. Now the {{sfn}} template is inserted in <ref> tags, but it is not used that way.

In T161958#11125907, @Sophivorus wrote:

Not sure I understand you. Are you suggesting using <cdx-popover> as the main component of the gadget? If so, I think it's a good idea, but would require a major rewrite. Would it give us a some concrete advantage worth the effort? Do you think it would somehow help solve the tooltip issue?

I wanted to create another task, but it is probably possible through this one. What if the main window is given the cdx-popover’ class?

Done.

It seems to me that abandoning the practice of translating global gadgets via translatwiki.net and using the translations at Commons is the worst way. Since the translation at Commons is extremely inconvenient and practically impossible to implement due to problems with the user interface. It is unreadable, it is impossible to edit it normally and search for untranslated strings.
I like the option with the fallback much more, or you can use gitlab-content proxy () https://ru.wikipedia.org/wiki/User:Iniquity/Gadget-script-installer-core.js#L-730.
https://wikitech.wikimedia.org/wiki/Tool:Gitlab-content

In T394916#11102654, @Sophivorus wrote:

Done! Translations are now hosted at https://commons.wikimedia.org/wiki/Data:Gadget-ProveIt.tab and fetched from there. Can be tested in the development version (see my common.js) and will be deployed in a few days.

In T400577#11078319, @Esanders wrote:

• Depending on how the [] are implemented, add some CSS padding or spaces either side of them

If you choose this way, be sure to check how it will look together with CheckUser-UserInfoCard.

As for the icons, I agree, but it is impossible to recreate the other components of the codex in this way: https://doc.wikimedia.org/codex/latest/components/overview.html

In T357463#11067810, @SD0001 wrote:

Not sure what you mean by that? Rendering images from commons is basic wiki syntax and doesn't require knowing scripts or updating styles.

In T357463#11060733, @SD0001 wrote:

Does it need to be an extension? Since codex is part of mediawiki core, I think it would be reasonable to put in core.

Or maybe this can be declined in favour of T361497. I'm not sure why there needs to a way to insert icons directly through the parser instead of just using them as normal images.

As a user, I want to have easy access to the basic forms provided by the codex for styling wiki pages. Without having to know scripts and constantly update styles.

In T355161#10984939, @DLynch wrote:

We talked about this in some Editing team meetings a while ago, and at the time we felt that we didn't think there were any security issues with it, but we wouldn't want to deploy this to WMF wikis without making some changes to how it works. I don't know whether you'd like to put off formal security review until after anything like that happened...

I think it should also indicate the year (New articles from 2018), because I was very surprised to see that I created 4 articles :)

In T400687#11044187, @Dreamy_Jazz wrote:

We can still define GENDER in the message, but the gender in this case would default to unknown to use the gender-neutral text.

In T400687#11043682, @Dreamy_Jazz wrote:

checkuser-userinfocard-error-no-data

We may not be able to properly support GENDER in this message, because we get the gender of the user using the API and the above message is displayed if the API returns nothing. We could just provide unknown as the gender always if that works?

To avoid overloading the system and check more edits, it can be replaced the label from "no edits" to "no data" and make part of the graph gray.

I think this would be useful not only in DiscussionTools but also in Convenient-Discussions :)
fyi @Jack_who_built_the_house

I have create a JSON file with actual fallbacks list: https://www.mediawiki.org/wiki/Manual:Language/fallback-languages-list.json

@bd808 As it turns out, the task already exists :) I also encountered this today.