That's fine of course, since it solves the problem. But it's good to keep this in mind for any future popups, that they shouldn't be shown to people who never saw the old version. :-)

In T367213#9881386, @bd808 wrote:

I believe this would need to work by adding something to the WikimediaDebug extension that changes what is rendered on the page. There are some methods for sniffing for an installed extension in Chrome that might work, but Firefox appears to have closed those same loopholes to reduce browser fingerprinting options.

Deployed

In T367674#9896701, @Dcljr wrote:

Is this in response to a request from that community? If so, please link to the discussion. If not, why do you think this needs to be done? (What problem are you trying to solve?)

In T367083#9879667, @Raymond wrote:

@jhsoby This task is mainly about the fact that {{int:citoid-citoiddialog-mode-manual}} is not parsed. Do you think it is still a dupe?

In T364742#9803435, @Raymond wrote:

When writing this task I was not aware that a non-breaking space was the issue.

Yes, I too think the approach @Tacsipacsi suggests is the best one.

(Other assignee – for the move main page part)

As I understand it now, they would be able to add or change languagename-xx messages too, but the message documentation would show a warning for it. (But I think there’s a legitimate use case for it – sending a translation to translatewiki and CLDR at the same time, and then having it in production via translatewiki without having to wait for the next CLDR release.)

So is the idea that CLDR will populate both the languagename-xx and languagename-xx-override messages, and translators in Translatewiki will have access to changing/adding translations to the languagename-xx-override messages only?

Suggestion: Add a "watchlist star" to each group in Special:LanguageStats. Possibly this page can also be sorted to show your favourites (i.e. watched groups) first?

The change should be available on relevant wikis by Thursday next week

I already made some comments about this in the relevant patch, but they've gone unanswered (presumably because the patch is already merged), so I'll copy them here:

• Create the wiki at some other name like "mos-x-deconflict.wikipedia.org" (using the BCP47 private subtag syntax is probably the least bad). This would work, probably without major changes, but doesn't feel right.

This is a no-go from my POV. We're trying to minimize the amount of irregularities on Wikimedia language codes vis-à-vis ISO codes, and this would break with that.

In T363538#9747595, @Bugreporter wrote:

List of pages that will be affected:

Generated using Wikimedia Global Search on 2024-04-26 11:28

That list is not exhaustive, because there are a lot more in enwiki.

I am not nearly done, this one's really time-consuming.

This happens because the selector .ext-campaignevents-details-participants-container .ext-campaignevents-details-participants-table .ext-campaignevents-details-participants-table-header th has position:sticky; z-index: 100;.

Please state what the name of the namespace and its talk namespace should be in Malayalam.

In T362441#9711103, @Snaevar wrote:

The largest thing here would be having the current namespaces as aliases, especially in the Template and Module namespaces. This will create a massive mess otherwise, although it will only be for a while.

Hi @Stefan-Orvar-Sigmundsson, and thanks for this very thorough task!

To test, go to https://www.wikidata.org/wiki/Q42?useskin=timeless&uselang=he

I believe this (and T361137) is https://github.com/notofonts/noto-fonts/issues/736

In T359101#9700796, @Reedy wrote:

Timeless is showing:
[…]

In T362125#9700720, @Nikerabbit wrote:

As @jhsoby pointed out https://www.mediawiki.org/wiki/Extension:VisualEditor#Changing_active_namespaces says we should use namespace names instead of ids (why? everything else uses ids). Maybe we didn't test this change properly.

I found that information via this topic on mw:Extension talk:VisualEditor, which is the top Google hit for "wgVisualEditorAvailableNamespaces". The last comment by kghbln linked to a thread on the now-defunct discourse-mediawiki.wmflabs.org, and I just edited the link to point to an archived version. In there, kghbln points out something interesting: You can add namespaces to wgVisualEditorAvailableNamespaces using the ID (or constant), but to remove them you have to use the English canonical name.

I don't see this on my system. Looks like a font issue. Could you compare the fonts used for that page in Timeless vs. Vector in the console and remove some of them to see if a font is the culprit?

Aye, thanks!

This bug is very similar to T344596, where @thiemowmde has mentioned T346252. Possibly/probably related?

If we had this, it could help prevent bugs like T360066 and T361695. The former bug happened because an illegal title character made it into a message that forms a page name, and the latter happened because log titles need to be unique within a language. So if we could tag page name messages and log title messages as such, we could add validators that prevent bugs like that from happening again.

With the closing of T63007: Allow specifying when a gadget should load (action, namespace, content model), especially the patch rEGADe2cb01ddcd66: Add support for categories in definitions, I think the premise for this task is also fulfilled. This task has been about using a magic word to add gadgets only to certain pages, but you can achieve the same by adding the pages you want to a (probably hidden) category that is only added to the pages the gadget is needed on.

Thank you very much for fixing this! All looks good now. :-)

Lucas said in Telegram that he couldn't reproduce it either. Really weird.

The change in a9a9b1976f (and my follow-up in 9cb1af627a) is working as intended now (for reasons unknown to me, it can take a while between merging a validation exclusion change and it actually working), so I think this can be closed. You'll still have to manually go through each message in https://translatewiki.net/wiki/Special:Translate?filter=!translated&action=page&language=he&group=ext-wikimediacreativecommonslicensetexts and hit "save" though, because the messages have changes (but Raymond's automatic text replacement should have already fixed updating the links).

Wouldn't parsing be better if it's possible? I can imagine some languages may have a convention of putting "foreign terms" like JavaScript in italics, for instance.

Patch for review: