In T314727#8463567, @alexhollender_WMF wrote:

@Iniquity: the heading of the page/article is a dense area, and the lines help to separate the various parts (page header, page toolbar, page content). Moving the From wikipedia... tagline below the page title makes the heading area look unbalanced, and gives the tagline too much emphasis.

I think you are right and we need to remove this link from the menu and move it to the first level of ULS. Smth like that:

Hello! Maybe you are right and I was just too surprised that some of the messages appeared in English. It's just that most of the sidebar used to be controlled MediaWiki:Sidebar including the headers. Therefore, the first thing I did was get into the MediaWiki:Sidebar, and only then did I start looking through &uselang=qqx. Just in one essentially the menu - two different behaviors. And it's not entirely clear, maybe you just need to get used to it. If you do not see this as a clear problem, then we can return to this later.

In T328069#8641264, @Patriccck wrote:

This is how it looks on 15,6" notebook (cs.wikipedia.org).

1. Overlapped text.
2. I don't like also the second sliding bar but it is probably necessary for smaller displays.
3. Cat-a-lot overlaps V22 button.

Per chat with @Urbanecm.

In T329721#8628757, @Aklapper wrote:

I don't consider this a bug but a feature request. There needs to be a cut at some width.

Yes, for Russian we have the same problem:

On Polish Wikipedia we have tools like "Report a bug". This should be visible for all users. And should be easily accessible.

Add idea for CWS2023: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Notifications,_Watchlists_and_Talk_Pages/Allow_posting_new_sections_to_top_of_Talk_pages

I think I come here with Russian Wikipedia soon.

I have one more question, does it bother you that this text ([hide]) repeats the text in navboxes and other collapsed blocks, but works in a completely different way? It stumped me, for example. Maybe change it to [collapse] or [unpin] or smth else?

In T327847#8576648, @Iniquity wrote:

Wow, yes, of course it should be removed. Because these extensions are clearly not meant to be a regular userbox. I don't know why it was added, to be honest.

I understood why it was added there - to explain the mechanics of adding pseudo-language templates that are not in ISO. For example: hangul, ipa, css, cyr etc. Not all userboxes are pseudo-languages and therefore not all of them should be included in the main block.

In T327847#8576541, @Tacsipacsi wrote:

In T327847#8576107, @Iniquity wrote:

Everything else is regular userboxes that should not be inserted into the Babel.

The extension page takes User from London as an example. Should that not be inserted into the Babel? Then why is it an example?

Wow, yes, of course it should be removed. Because these extensions are clearly not meant to be a regular userbox. I don't know why it was added, to be honest.

In fact, no, a separate template is created, in the subpages of which their css are published. Or can ask the admins to change the content model.

Yes, exactly creating a ton of separate templates is what results in a mess.

No, I'm not talking about that. You create one template, and create CSS on its substation. For example: https://test.wikipedia.org/wiki/Template:Userbox/iniquity.css

In T327847#8575823, @Tacsipacsi wrote:

In T327847#8573880, @Iniquity wrote:

By the way, I'm not very sure that you need to change something in the content of the babel userboxes. Do you have examples?

Sure. {{User Facebook}}, {{User contrib}} etc. (I didn’t check if they’re actually used within {{#babel:}} boxes or only using legacy babel templates, but they could well be.)

These are not babylon templates, babylon templates only support language and pseudo-language templates. Everything else is regular userboxes that should not be inserted into the Babel.

In T327847#8573523, @Tacsipacsi wrote:

In T327847#8568917, @Iniquity wrote:

I'm not sure that we need to support single template parameters, That's something scary. For personal design, you can always use TemplateStyles.

How would you change the content using TemplateStyles? It’s for styles.

It shouldn't be manual, it should be semi-automatic: T228598. Moreover, all userboxes in almost all projects have a align setting. Babel creates userboxes. And the problem with the lack of such a setting for Babel userboxes at one time gave me problems.

In T66164#8571830, @Nikerabbit wrote:

It was mentioned above that this can be handled by a wrapping babel in a div. What benefit is there to support this in the Babel itself?

I'm not sure that we need to support single template parameters, That's something scary. For personal design, you can always use TemplateStyles.

Thanks! @Pppery, can you please check if this overlaps with your patches? :)

I really don't like that our descriptions are built on a CERF scale and don't match to ILR scale. They should be updated.

In T173700#8566634, @Amire80 wrote:

In T173700#8566620, @Iniquity wrote:

@Amire80, @Nikerabbit Hey! Do you think that a separate task is needed to fix work with languages in MediaWiki?

What do you mean by "work with languages"?

In T328193#8566630, @Umherirrender wrote:

In T328193#8566617, @Iniquity wrote:

In T328193#8566610, @Umherirrender wrote:

Are you requesting a new feature to have a new message with a template shipped with Babel extension? That sounds wrong.

Yes, that's exactly what I'm talking about. Why wrong? If you tell the extension during installation that you need to create a certain template in order for the categories to start being created. I don't really see any other way.

The extension is usable without any changes to the wiki currrently. When a community wants a specific template it would change the message to that template, but it can already control the wikitext for new category pages, so I see no need to have a second way doing that and making things complicated.

There is a problem here, to realize that you need a template, it can take a long time. And during this time, a huge number of categories will be created.

@Amire80, @Nikerabbit Hey! Do you think that a separate task is needed to fix work with languages in MediaWiki?

In T328193#8566610, @Umherirrender wrote:

Are you requesting a new feature to have a new message with a template shipped with Babel extension? That sounds wrong.

Yes, that's exactly what I'm talking about. Why wrong? If you tell the extension during installation that you need to create a certain template in order for the categories to start being created. I don't really see any other way.

Since the extension uses the ILR scale, it has an extended level, for example, 0+, 1+, 2+, 3+, 4+: https://en.wikipedia.org/wiki/ILR_scale. A complete system adaptation would be helpful.

I fixed it here: T178782. There are only languages with long names left (simple, be-tarask etc), but it seems to me that this is ok.

Given that categories can be renamed in the future, you need to focus on the English language or the Wikimedia Commons category in the element. That is, check when creating in all elements containing Q20010800, the text: User %code%. Or, in general, request separate qualifiers for elements in the wikidata: this will make it much easier to catch the desired element.

The problem still exists: https://en.wiktionary.org/wiki/Special:Contributions/Babel_AutoCreate

@Shizhao Hello! Can you please elaborate on the problem? Now it is not clear what it is.

In T33115#8566316, @Pppery wrote:

Is https://www.mediawiki.org/w/index.php?title=Extension:Babel&diff=prev&oldid=5740973 sufficient for this, or is something else needed?

Yes, as a minimal fix - it's great :) Thank you! And in the future, I thought that we could make a setting in Community Configuratuion: show/hide footer/header T328171.

Created a separate task on how this problem can be solved in the future: T328193.

It's extremely unsafe to let an automated bot overwrite the text of multiple categories.

In T33115#8566265, @Iniquity wrote:

There are actually two tasks here:

1. Document or change how the header and footer are hidden. It's not really obvious, and a separate task is needed.
2. Do not display or modify the block if categorization is disabled, all category settings are set to "false". It seems to me that this is a waste of too many resources for a small result (and I'm still not sure if it's the right thing to do).

In T33097#8566266, @Pppery wrote:

But I would duplicate it with one more parameter anyway, because it's a footer, not a "main category store" :)

I'm not convinced. This decision will ultimately be made by whoever code-reviews the patch.

There are actually two tasks here:

1. Document or change how the header and footer are hidden. It's not really obvious, and a separate task is needed.
2. Do not display or modify the block if categorization is disabled, all category settings are set to "false". It seems to me that this is a waste of too many resources for a small result (and I'm still not sure if it's the right thing to do).

In T33097#8566245, @Pppery wrote:

In T33097#8566205, @Iniquity wrote:

In T33097#8566176, @Pppery wrote:

Sorry for the indecisiveness.

:) Thanks for claimed it!

There is one problem with MediaWiki:Babel-footer-url. I remembered this when I looked at this problem - T33115. In Russian Wikipedia, I generally reassigned and removed the link to the category from the footer: https://ru.wikipedia.org/wiki/Шаблон:Babel#Пример_использования, https://ru.wikipedia.org/wiki/MediaWiki:Babel-footer-url. And I think it will be difficult to find out where else this message has been changed. To get the main-main category, a new parameter is needed.

My in-progress patch passes any categories to add as a parameter to MediaWiki:Babel-autocreate-text-main and MediaWiki:Babel-autocreate-text-levels. Any wiki doing something weird with MediaWiki:Babel-footer-url (although I'm not sure what Russian Wikipedia is doing there since I don't speak Russian) can also add its own parent categories to MediaWiki:Babel-autocreate-text-main and not use the parameter.

In T33097#8566176, @Pppery wrote:

Sorry for the indecisiveness.

In T328171#8566170, @Pppery wrote:

I've added documentation for the setting.

It looks like there is another setting wgBabelCategorizeNamespaces. I don't know how it works, not documented.

It might be interesting to add the basic category ($wgBabelMainCategory and $wgBabelCategoryNames) settings that are currently in the config file to the community config: T323811.

I understand correctly that this task is not subtask and it is a duplicate of T165118? :)

I think this is a good idea :) Can also make a setting that would show all mentees / only active mentees.